Export package.json so tools can more easily access meta data #2317
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File size impactMerging export-package-json into master will not impact files in any group. browser (0/2)No impact on files in browser group. node (0/1)No impact on files in node group. extras (0/8)No impact on files in extras group. |
joeldenning
approved these changes
Apr 7, 2021
|
This is released in https://github.com/systemjs/systemjs/releases/tag/6.10.0 |
1 task
|
Thanks! |
This was referenced Jun 10, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'd love if I could use the traditional
nodejs -p "require.resolve('systemjs/package.json')"to find the module root directory.
with current master:
with my branch: