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 :
>
> On Wed, Nov 07, 2018 at 05:32:40AM -0800, Martin Husemann wrote:
> > I understand the
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 of
I wonder if ChakraCore (the JS engine used inside Edge) has a JavaScript
interpreter that would make it viable to run node-chakracore (
https://github.com/nodejs/node-chakracore) to run on sparc64. Have you
tried that by any chance? (Of course even if that works, how compatible
the node_modules u
On Wed, Nov 7, 2018 at 5:35 AM 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 relea
On 11/7/18 9:30 AM, Martin Husemann wrote:
Or port node to Spidermonkey, might be easier :-)
True. https://github.com/mozilla/spidernode/ is not really active, but
might be revivable...
-Boris
___
dev-builds mailing list
dev-builds@lists.mozilla.o
On Wednesday, November 7, 2018 at 3:23:02 PM UTC+1, Boris Zbarsky wrote:
> You'd need to port V8 to work on sparc, right? That sounds fairly
> painful...
Or port node to Spidermonkey, might be easier :-)
___
dev-builds mailing list
dev-builds@lists.mo
On 11/7/18 8:32 AM, Martin Husemann wrote:
NodeJS seems to have no support at all for sparc CPUs, and I am not yet sure
how hard it would be to add.
You'd need to port V8 to work on sparc, right? That sounds fairly
painful...
-Boris
___
dev-build
7 matches
Mail list logo
