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

npm start with autoreload #2426

Closed
techtonik opened this issue Nov 29, 2018 · 6 comments · Fixed by #3401
Closed

npm start with autoreload #2426

techtonik opened this issue Nov 29, 2018 · 6 comments · Fixed by #3401
Labels
developer-experience Dev tooling, test framework, and CI

Comments

@techtonik
Copy link
Contributor

📋 Description

In TUTORIAL.md I need to start and stop npm server every time to load new changes? That's cumbersome. Is there any autoreload mechanism for /services/?

@techtonik
Copy link
Contributor Author

Found https://github.com/remy/nodemon Is it Good?

@paulmelnikow
Copy link
Member

Yea… the frontend reloads when it changes, but it doesn't pick up changes to the badge examples until npm run examples is run again. If that happened automatically, that's something I would find quite handy.

The services do not reload either, though I haven't found that to be a significant problem since I do most of my work through the test runner.

Do you mean live editing of TUTORIAL.md? That's something else entirely.

@paulmelnikow paulmelnikow added the developer-experience Dev tooling, test framework, and CI label Nov 29, 2018
@techtonik
Copy link
Contributor Author

I followed the tutorial and found it too cumbersome to restart server on every change to example service. nodemon is good, but it keeps reloading all the time. Probably because vim updates some temporary file there.

@paulmelnikow
Copy link
Member

How were you testing it?

@techtonik
Copy link
Contributor Author

I don't remember. There is no proposed way for autoreload in this project, so probably it was:

nodemon ./server.js

paulmelnikow added a commit that referenced this issue Apr 30, 2019
While working on #2428 I found myself wanting to reload the server frequently. This is working great and reducing my iteration time significantly. I should have tackled this way sooner! :P

I’ve left verbose on which seems useful, at least in the short term while we’re tuning the configuration.

Close #2426
paulmelnikow added a commit that referenced this issue Apr 30, 2019
While working on #2428 I found myself wanting to reload the server frequently. This is working great and reducing my iteration time significantly. I should have tackled this way sooner! :P

I’ve left verbose on which seems useful, at least in the short term while we’re tuning the configuration.

Close #2426
@paulmelnikow
Copy link
Member

I opened #3401 which adds nodemon. I tweaked the config a bit – it is only watching .js files – though it may be necessary to ignore some more files. The verbose option is on, so it should print what is triggering the reload.

If you take it for a spin and notice anything else that needs adjusting, let me know!

paulmelnikow added a commit that referenced this issue May 1, 2019
While working on #2428 I found myself wanting to reload the server frequently. This is working great and reducing my iteration time significantly. I should have tackled this way sooner! 🙊 

I’ve left `verbose` on which seems useful, at least in the short term while we’re tuning the configuration.

Close #2426
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
developer-experience Dev tooling, test framework, and CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants