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?
2 years ago
We know this as have started migrating away... slowly...
We've started migrating, and most major services have migrated.
John, were you leading this? I feel like just about everything is migrated now, but I'm not sure who has that status..
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.
Yes, this was a project that I completed. Greg is right that the only outstanding thing is docker-worker.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.