So, am I getting this right: node-forward="Community effort to strengthen node and its ecosystem by providing a source for knowledge directly from the horses mouth" io.js="Community effort to bring node forward with help from node-forward" ?
I hope @dshaw, @rvagg et al herd all concerned into a NodeUp episode ASAP.
the changelog also wanted to get a podcast up
Debian/Devuan, also? FFS. Two major deps with communities forking.
"Freedom isn't free" Team America - 2004
I have some idea for node that might be interesting: How about a "auto-refresh" command-line option. if any of the loaded and/or required files changed then the process is automatically restarted.
@martinheidegger I don’t think it should be handled at node level. May be the task runner that you use with your projects should be implementing this.
@martinheidegger I believe nodemon can do this.
Yeah @martinheidegger look up supervisor or nodemon. And while we're at it, also gulp or grunt.
gulp and/or grunt are not the "automatic-good-to-teach" solutions i am looking for, they are hard to handle properly . I didn't know that nodemon was able to do that (last time i checked it didn't). pm2 seems to support it too (sweet). The argument in my head to support it on a platform level was that beginners struggle with the running of apps very often. "I changed the file, why does the server not update?" "Why do I have to restart now?", ... I recognised this topic when I talked with a Meteor developer. He simply assumed that live-reload is normal and every tool supports it. I found it very nice way to think.
That's actually a legacy from PHP, RoR and similar, I think - to expect stuff to reload automatically.
As for automatic-good-to-teach solutions, I prefer gulp over grunt as grunt is more configuration, gulp looks like regular node.js code.
So you might learn something using it.
But the thing is - you start learning good practices: like using a proper tooling for everything. When you work with, say, Java, and do a change, Eclipse will save the stuff for you, compile, hot-load the class or reload the app or something, so you deal with development, not with minifying assets or bootstraping stuff, you get a nice workflow that most Node.js developers will be able to understand and follow.
Anyway, I didn't see you ask for a 'good-to-teach' solution, you asked about restarting node.js and apps on the platform level. People (including me) suggested existing solutions like supervisor and nodemon and as you say, pm2. I think it's still a part of the platform as those are the typical tools you'd use anyway. But since they do help you out some, I suggested that you also look into gulp or grunt.
So, maybe a misunderstanding on my side :smile:
Anyway, there you go.
+1 for nodemon
Does one of the node school.io core classes introduce nodemon?
@zladuric I don't suggest that this --watch switch should be there by default but at least as option. There is a reason why it has been successful in PHP/RoR/...
@LegitTalon there isn't a nodemon workshopper yet. Would you be interested in building one?
maybe a more general "node tools" workshopper
@olizilla Yeah, actually that sounds cool. I’m working on updating levelmeup to the latest workshopped and I’m sure by the end I’ll be familiar enough with the workshopper tools to make the node tools workshop
but who will make the workshopper workshopper
you knows it
that'd actually be super handy
nice one @LegitTalon, shout if you want a hand
yeah @LegitTalon the node tools workshop sounds cool, i’d be interested in following along with that too, helping where i can if needed
Hi there! Is node-forward is still intended to sustain? I couldn't see much going on in the repositories and in these chats. Thanks, Emanuel