yeah, and existing browser engine is amuh better GUI than we’d be able to just implement.
is there a discussion/place to discuss build targets for node?
yeah, there is a /build repo :)
that's where the people who are building and managing the new build system are
@rvagg is driving it
@quarterto No I don't mean node-webkit. I mean an access to node without the shell. I know that this thought is sort of heretic but having settings for npm, managing global packages or projects could perhaps use a user interface.
@martinheidegger I'm having trouble wrapping my head around what you are asking for. I read this as GIU configuration tool for package.json files? I've seen something like this for rails apps once: https://github.com/RailsApps/rails-composer
@evantahler Well: If you install nodejs on a mac these days all you "get" is a command line tool. Don't get me wrong: its cool. But for beginners it is sort of a black box. I think a UI could do following. 1) Offer a tutorial to get started with the first nodejs code 2) Offer a tool / display to set the global npm settings (and show them): npm set / npm get etc. 3) Offer a tool that lists the npm packages (particularly the ones that are often installed with -g) to install them globally (i.e.: coffeescript) 4) Offer a tool where you can add folders as "projects". Every project added has automatic (visual!) checks for the validity of the package.json (Eventually outdated dependency checks) buttons for all the enabled scripts (run/publish/etc.)
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.