-
Notifications
You must be signed in to change notification settings - Fork 43
Node.js Foundation Modules Team Meeting 2019-01-16 #248
Comments
Please take notice that we have an extra 5 minutes of unclaimed time. We can use that to go over or add an agenda item. |
I was hoping @guybedford could give a demo of his branch that implements the package exports and file specifier resolution specs. That could go in those timeboxes or we could add it as 5 minutes? https://github.com/guybedford/node/tree/irp-implementation / nodejs/ecmascript-modules#22 Update: added. |
I'm going to miss this week. I'll be speaking at CovalenceConf. |
I will not be able to attend. |
I will also miss today's meeting. |
I've posted a discussion about "exports" for CommonJS here - jkrems/proposal-pkg-exports#26. |
If anyone would like to try the demo from the talk, the build files are now available at: https://nodejs.org/download/test/v12.0.0-test20190116irp-mode-implementation/ This can also be compared against the build without "mode": "esm" using "exports" only as the ".js as ESM" indicator: https://nodejs.org/download/test/v12.0.0-test20190116irp-implementation/ If you find any bugs please post to https://github.com/guybedford/node/. For spec discussions, feel free to open an issue on the appropriate spec (https://github.com/GeoffreyBooth/node-import-file-specifier-resolution-proposal, https://github.com/jkrems/proposal-pkg-exports/, https://github.com/guybedford/ecmascript-modules-mode). |
Time
UTC Wed 16-Jan-2019 20:00 (08:00 PM):
Or in your local time:
Links
Agenda
Extracted from modules-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
Updates (10 minute timebox)
Approving PRs (5 minute timebox)
Discussion (40 minute timebox)
Invited
Notes
The agenda comes from issues labelled with
modules-agenda
across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.Joining the meeting
The text was updated successfully, but these errors were encountered: