This repository was archived by the owner on Sep 2, 2023. It is now read-only.
--eval, STDIN, and extensionless files#251
Merged
MylesBorins merged 2 commits intonodejs:masterfrom Jan 30, 2019
Merged
Conversation
ljharb
reviewed
Jan 21, 2019
Co-Authored-By: GeoffreyBooth <GeoffreyBooth@users.noreply.github.com>
targos
approved these changes
Jan 30, 2019
devsnek
approved these changes
Jan 30, 2019
ljharb
approved these changes
Jan 30, 2019
Member
Author
|
Thanks. If anyone wants to be involved in breakout discussions of how do handle ESM in entry points in Node, please comment here. I’ll add the interested people to the breakout teams section of the project board: https://github.com/nodejs/modules/projects/6 |
This was referenced Feb 15, 2019
This file contains hidden or 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
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.
Building off of the implementation of the “Package Exports” proposal and the “File Specifier Resolution” proposal, I think we can move on to figuring out how to support ESM input via
--eval, STDIN and extensionless files.Anyone interested in forming a small group to hash these out?