Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make it easier to tinker with internals inside of a node_modules directory #51

Open
jwarkentin opened this issue Oct 12, 2017 · 0 comments

Comments

@jwarkentin
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant