Ref https://twitter.com/thejameskyle/status/827993163348353025
https://unpkg.com/[email protected]/message.js
This would be similar to how we used to have babel-core/register -> babel-register
I guess we don't have to remove babel-node from babel-cli unless we want to make that breaking change..
cc @JonnyBurger (can you transfer me the npm package (@hzoo))
make build after a source code change or better just run make watch in another terminal window to auto run babel while you are developing packages folder called babel-node and copy the package.json/npmignore/setup files from another packageHi @hzoo,
If you don't mind I can pick this up.
... copy the package.json/npmignore/setup files from another package
Would it be better if the target package is babel-cli?
And before I make the pull request. This what the babel-node folder looks like. Did I miss anything?
.
โโโ README.md
โโโ index.js
โโโ package.json
โโโ src
โย ย โโโ _babel-node.js
โย ย โโโ babel
โย ย โโโ babel-external-helpers.js
โย ย โโโ babel-node.js
โโโ test
โโโ fixtures
โโโ index.js
4 directories, 7 files
Would it be better if the target package is babel-cli?
Yeah good idea
Right, whatever is necessary to make it work on it's own. Can check that the necessary deps are in package.json since you might not need everything.
So this means you probably don't need src/babel/* or babel-external-helpers.js, and you'll want the bin folder https://github.com/babel/babel/blob/master/packages/babel-cli/bin/babel-node.js + add bin in package.json
Most helpful comment
Hi @hzoo,
If you don't mind I can pick this up.