Straw man mozilla-central node_modules policies; comments requested

[For those who have seen earlier iterations of this document, the security section now discusses the recent event-stream/flatmap-stream exploit specifically --dmose] I’ve drafted a set of straw man proposals for getting basic node_modules support in mozilla-central sooner rather than later.

landing --enable-node by default shortly: today, Thursday, Aug _16th_

It has been pointed out that I made a mistake in my previous announcements -- today, Thursday, is August 16th, not August 17th. Sorry about that! I'm still going to go ahead and land this change shortly, because doing it now gives us more time before soft-freeze to shake out any issues that

devs: please install NodeJS; it will be required by default on Thurs, Aug 17th

This Thursday, August 17th, we’ll be turning on —enable-nodejs in the mozilla-central build system by default. This means that, for developers who haven't yet run `mach bootstrap --no-system-changes`, the build may stop working until that happens. For those on Mac, Windows, and many recent

Re: Intent to require Node to build Firefox 61 and later

Am Mittwoch, 28. Februar 2018 16:23:43 UTC-8 schrieb Nicholas Alexander: > For the reasons outlined at > https://docs.google.com/document/d/1tOA2aeyjT93OoMv5tUMhAPOkf4rF_IJIHCAoJlwmDHI/edit?usp=sharing, > we would like to make Node a requirement to build Firefox sometime in the > Firefox 61

Re: JSBC: JavaScript Start-up Bytecode Cache

Does this cache bytecode for about: pages as well? As an example, caching bytecode for various JS scripts from resource: and chrome: for about:home might get interesting startup improvements... Thanks, Dan ___ dev-platform mailing list