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
Since everything is built with webpack right now, it's difficult to tinker with the code as a dependency of another project. I don't like this. It should be trivial to get up and going for development on Node Monkey or to just tinker when needed. At the same time, I don't want to lose the benefits of Webpack such as being able to use newer ES features, build optimizations, the ability to easily recompile and target different platforms or the ability to inject configuration into builds.
It might be possible to provide a simple script that can be run to set it up and start watching for changes. Would it also be possible to easily notify users dabbling in the code that they need to run the command for their changes to take effect?
Another interesting possibility could be to monitor the source files from Node Monkey itself when NODE_ENV is not set to production and if it sees changes it could post a notice to the console at the very least and maybe even automatically recompile.
The text was updated successfully, but these errors were encountered:
Since everything is built with webpack right now, it's difficult to tinker with the code as a dependency of another project. I don't like this. It should be trivial to get up and going for development on Node Monkey or to just tinker when needed. At the same time, I don't want to lose the benefits of Webpack such as being able to use newer ES features, build optimizations, the ability to easily recompile and target different platforms or the ability to inject configuration into builds.
It might be possible to provide a simple script that can be run to set it up and start watching for changes. Would it also be possible to easily notify users dabbling in the code that they need to run the command for their changes to take effect?
Another interesting possibility could be to monitor the source files from Node Monkey itself when
NODE_ENV
is not set toproduction
and if it sees changes it could post a notice to the console at the very least and maybe even automatically recompile.The text was updated successfully, but these errors were encountered: