You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been thinking about implementing another binary for running the package in development mode..
Ideally such a command will:
Store the code generated by Babel in-memory
Watch the project files and reload on change
I would go with implementing that with pm2 or nodemon and executing babel-node each time.
However, @mishguru/package binaries use programmatic hooks to tap into babel but babel-node does not have a programmatic interface (not an "official" one anyway)..
Possible solutions:
I guess I can still use a module bundler like webpack for this and use it's bindings with Babel but it seems as a bit of an overkill..
I can use a bash script but that would be inconsistent with the rest of the library.
I can require them babel-node main module by requiring it directly (require('babel-node/src/babel-node')
Any ideas or suggestions are welcome [=
The text was updated successfully, but these errors were encountered:
It will.. The watch flag is really handy but it will still output files
while @babel/node would hold them in memory.
That is a viable solution though.. I’ll read a bit about the performance
differences.
I've been thinking about implementing another binary for running the package in development mode..
Ideally such a command will:
I would go with implementing that with
pm2
ornodemon
and executingbabel-node
each time.However,
@mishguru/package
binaries use programmatic hooks to tap intobabel
butbabel-node
does not have a programmatic interface (not an "official" one anyway)..Possible solutions:
webpack
for this and use it's bindings with Babel but it seems as a bit of an overkill..babel-node
main module by requiring it directly (require('babel-node/src/babel-node')Any ideas or suggestions are welcome [=
The text was updated successfully, but these errors were encountered: