For better and for worse, I believe that's no longer true: devtools is now using it to transpile JSX files to JS files as part of the normal build.
Dan Am Do., 8. Nov. 2018 um 13:55 Uhr schrieb Mike Hommey <m...@glandium.org>: > > On Wed, Nov 07, 2018 at 05:32:40AM -0800, Martin Husemann wrote: > > I understand the desire for developers do use the best tool for each job, > > and integrating NodeJS in the regular work flow during development might be > > a good idea. > > > > However, requiring NodeJS for each build (including the official releases) > > causes great problems: NodeJS itself is way less portable than Firefox, and > > I am building one of the strangler platforms - on sparc64. NodeJS seems to > > have no support at all for sparc CPUs, and I am not yet sure how hard it > > would be to add. I will investigate (as time permits). > > > > So I have a concrete question: are the outputs of the NodeJS runs during a > > build actually target machine / OS dependent? At first I would hope not, > > and in this case: would it be possible to pre-generate the NodeJS output > > files for each official release, and then allow building with those > > pre-generated files instead of a local NodeJS installation? > > > > Note that for your _immediate_ needs, you can just --disable-nodejs, > because node is currently *not* actually used for anything. That won't > be the case for very long, though. > > Mike > _______________________________________________ > dev-builds mailing list > dev-builds@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-builds _______________________________________________ dev-builds mailing list dev-builds@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-builds
