This repository has been archived by the owner on Aug 4, 2021. It is now read-only.
Add support for es2015 field #186
Closed
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
|
This change would be helpful downstream in bazelbuild/rules_nodejs#429 and angular/angular#27220. |
|
Better to achieve this via #182 |
|
Closing in favour of #182 |
|
It's not stalled. Maintainers don't have free time to finish it. And we wouldn't like to add a feature which will be removed later. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The
es2015package.json field is part of both angular and rxjs npm packages. Default is set to false so as not to change the current behavior.For reference, https://www.npmjs.com/package/rollup-plugin-node-resolve-angular and https://www.npmjs.com/package/rollup-plugin-node-resolve-next both handle the
es2015field.