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 development cycle. (Firefox 60 will be an ESR release, so this > provides a complete ESR cycle without requiring Node.) >
>From the narrow viewpoint of Activity Stream, this will make things a bunch >better for us, as well as other teams we work with. The biggest win here will >be that it will avoid us checking in build artifacts, so that changes become >smaller and easier to analyze. >From the bigger Mozilla viewpoint, this strikes as a big win, since a huge >chunk of the world's JavaScript tooling output is primarily available from the >npm ecosystem, and it should allow us to take thoughtful dependencies on >things that will make us much more efficient, rather than forcing us to >write/maintain so much of our own stuff. Thanks for writing up such a thorough and thoughtful analysis. Dan _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
