Closed
Bug 1224170
Opened 9 years ago
Closed 8 years ago
Apparently, we shouldn't be using babel-node in production
Categories
(Taskcluster :: General, defect)
Taskcluster
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: pmoore, Unassigned)
Details
From: https://babeljs.io/docs/usage/cli/ > ** Not meant for production use ** > > You should not be using babel-node in production. It is unnecessarily heavy, > with high memory usage due to the cache being stored in memory. You will also > always experience a startup performance penalty as the entire app needs to be > compiled on the fly. We should probably transpile, and then run the transpiled code... Do we lose anything if we do it this way?
Reporter | ||
Updated•9 years ago
|
Flags: needinfo?(jopsen)
Comment 1•9 years ago
|
||
We know this as have started migrating away... slowly...
Flags: needinfo?(jopsen)
Comment 2•8 years ago
|
||
We've started migrating, and most major services have migrated.
Comment 3•8 years ago
|
||
John, were you leading this? I feel like just about everything is migrated now, but I'm not sure who has that status..
Flags: needinfo?(jhford)
Comment 4•8 years ago
|
||
The one thing that has not been converted is the worker, but I think that will be part of the migration away from 0.12 that needs to happen soon.
Comment 5•8 years ago
|
||
Yes, this was a project that I completed. Greg is right that the only outstanding thing is docker-worker.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(jhford)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•