profile
viewpoint

Ask questionsOut-of-Band Meeting Proposal

Since yesterday's meeting it turns out we were able to work around the async bootstrap issues with a more conservative approach that gets all the tests passing on the experimental modules unflagging PR.

This means that if we can find consensus on requirements for release, there is a window for us to still meet the Node.js 12 LTS release which is on the 21st of October, two days before our next meeting.

In order for us to discuss this possibility, I'd like to propose we arrange an out-of-band meeting early next week. I've created a Doodle to find a shared time for this meeting here -https://doodle.com/poll/a4nvpv6tqf7cnu9g. Please fill this out when you can.

The resolutions from last meeting have now been implemented. I'd like to ask you all to please put some serious consideration to where we are on modules, and any considerations or feedback you have concerning a shippable implementation. It feels like we are very close here, but if we do not have consensus to release there will be other opportunities in future as well - lets see how discussion goes!

nodejs/modules

Answer questions MylesBorins

Anything that goes into 13 can be backported to LTS two weeks later. Since we are experimental / behind a flag we don't need to wait for a minor

On Fri, Oct 11, 2019, 5:10 PM Guy Bedford notifications@github.com wrote:

@targos https://github.com/targos I wasn't aware there was an LTS cutoff two weeks before, I guess we will have to apply further changes to the next minor then? Or can further --experimental-modules changes land on patch releases?

The goal here would be to be able to say "12 LTS --experimental-modules" is the current recommended implementation. But if we've already missed the cutoff for such a thing then certainly there is no need for an out-of-band meeting.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nodejs/modules/issues/399?email_source=notifications&email_token=AADZYV6G3PTHF2W3YQ7CPQLQODTWDA5CNFSM4I7UPAP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBBHD3A#issuecomment-541225452, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADZYV7I356VNXFN6UZD2F3QODTWDANCNFSM4I7UPAPQ .

useful!

Related questions

Transition Path Problems For Tooling hot 1
Proposal: Support loading package by own "name" hot 1
JSON modules are being reverted on web hot 1
node v13.0-v13.1 errors on require of a module with "exports" defined hot 1
Use consistent error codes for MODULE_NOT_FOUND hot 1
Loader Hooks hot 1
Proposal: Support loading package by own "name" hot 1
Github User Rank List