Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 01 01:35
    AtOmTurk starred node-forward/discussions
  • Feb 07 21:12
    netifork starred node-forward/discussions
  • Oct 29 2019 06:52
    Seia-Soto starred node-forward/discussions
  • May 24 2019 13:21
    sutjjang starred node-forward/discussions
  • Mar 12 2019 21:00
    binarygalwalkin starred node-forward/discussions
  • Jul 12 2018 20:28
    strugee commented #29
  • Jul 12 2018 17:55
    carlos8f commented #29
  • Jul 12 2018 16:49
    mathieumg starred node-forward/discussions
  • Jul 12 2018 16:19
    kmoe commented #29
  • Jun 26 2018 15:25
    sashahilton00 commented #29
  • May 22 2018 10:26
    CraigHarley starred node-forward/discussions
  • Mar 18 2018 22:45
    TeachMeAnything starred node-forward/discussions
  • Feb 13 2018 21:22
    bmeck commented #29
  • Feb 13 2018 21:20
    frio commented #29
  • Feb 13 2018 21:15
    frio commented #29
  • Aug 04 2017 17:42
    dstufft commented #29
  • Aug 04 2017 17:37
    bmeck commented #29
  • Aug 04 2017 17:22
    dstufft commented #29
  • Aug 04 2017 17:05
    bmeck commented #29
  • Aug 04 2017 16:11
    seldo commented #29
Evan Tahler
@evantahler
@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
Martin Heidegger
@martinheidegger
@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.)
Mikeal Rogers
@mikeal
yes :)
Martin Heidegger
@martinheidegger
yes?
Mikeal Rogers
@mikeal
@bnoordhuis @indutny @piscisaureus @trevnorris TC Meeting :)
Sam Mikes
@smikes
Right, so this article by Lauren Orsini: http://www.donotlink.com/ch53
seems not to have been informed by joyent/nodejs-advisory-board#1
gramergrater
@gramergrater
nice article, a bit long though
i do wonder though, for how long can joyent remain solvent?
gramergrater
@gramergrater
this thing is rad: http://nodered.org/
but i don't understand why ppl keep perpetuating "the internet of things"
wasn't that coined by the CIA chief?
Mikeal Rogers
@mikeal
joyent/nodejs-advisory-board#11
if you want to contribute to making Node a contributor driven project please comment on that PR :)
gramergrater
@gramergrater
dammit gitter why don't issues appear in vimp
can't even right-click new tab
"open in github" goes to gitter
damn why aren't we using irc?
Mikeal Rogers
@mikeal
my "open in github" opens in github :)
gramergrater
@gramergrater
vimp or vimfx?
Forrest L Norvell
@othiym23
@mikeal comment left
Andreas Marschke
@andreas-marschke
huh. I think some of the features I was looking for regarding performance measuring and monitoring have been implemented already: http://www.brendangregg.com/blog/2014-09-17/node-flame-graphs-on-linux.html
Cristian Wilgenhoff
@cwilgenhoff
This message was deleted
Andreas Marschke
@andreas-marschke
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" ?
Jeremiah Senkpiel
@Fishrock123
Node-forward = community efforts; io.js = node core (mostly code, roadmap also)
Jeremiah Senkpiel
@Fishrock123
(well, io core more specifically)
Talon
@talon
I like the way nodeschool.io is run with smaller communities coming together to mentor eachother and I wonder if that model can be applied to the node-forward mentoring program in some way.
Garth Kidd
@garthk
Anyone got a TL;DR of what happened with Node/io.js? Did the Joyent-driven governance smell too much like Dept. of Change Prevention to those invited?
Matt Hernandez
@fiveisprime
Isaac has a real nice writeup about it
Garth Kidd
@garthk
I hope @dshaw, @rvagg et al herd all concerned into a NodeUp episode ASAP.
Ta.
Gary Katsevman
@gkatsev
the changelog also wanted to get a podcast up
Garth Kidd
@garthk
Debian/Devuan, also? FFS. Two major deps with communities forking.
Oli Evans
@olizilla
"Freedom isn't free"
Team America - 2004
Martin Heidegger
@martinheidegger
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.
Boopathi Rajaa
@boopathi
@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.
Matt Brennan
@quarterto
@martinheidegger I believe nodemon can do this.
Zlatko
@zladuric
Yeah @martinheidegger look up supervisor or nodemon. And while we're at it, also gulp or grunt.
Martin Heidegger
@martinheidegger
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.
Zlatko
@zladuric

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.
Talon
@talon
Enter Yeomen.
Jason Rhodes
@jasonrhodes
+1 for nodemon