Live data from Hacker News

Habits of a Happy Node Hacker

blog.heroku.com

1–10 of 56 posts

Re: Habits of a Happy Node Hacker

#4

Regarding point 9, if you don't check your `node_modules` into version control don't you run the risk of them disappearing from NPM?

"If you are paranoid about depending on the npm ecosystem, you should run a private npm mirror or a private cache.

If you want 100% confidence in being able to reproduce the specific bytes included in a deployment, you should use an additional mechanism that can verify contents rather than versions. For example, Amazon machine images, DigitalOcean snapshots, Heroku slugs, or simple tarballs."

https://docs.npmjs.com/misc/faq#should-i-check-my-node-modul...

Re: Habits of a Happy Node Hacker

#6
post #3

Node.js is the rare example of a Linux-centric tool with great cross-platform support. Apart from the problems with Windows, npm, and path lengths.

There are hiccups, but as a general statement I stand by it.

"Node is pretty impressive on Windows. You get the feeling that JavaScript (as well as HTML and CSS) are a first class citizen in the Operating System. I already have a list of dozens of Native Windows Apps I want to build using Node."

http://daverupert.com/2015/08/developing-on-windows/

(good contrast with other experiences from a polyglot)

"Node is quite awesome on Windows to be honest."

https://medium.com/@vernonk/surface-pro-4-the-ipad-i-always-...

Re: Habits of a Happy Node Hacker

#7
post #3

Node.js is the rare example of a Linux-centric tool with great cross-platform support. Apart from the problems with Windows, npm, and path lengths.

There are a lot of problems, actually. I don't think Node.js has bad cross-platform support but calling it "great" is definitely a stretch. Node's APIs are very low-level and unix-centric and the result is it is very easy to make a library that doesn't work well on Windows because it assumes unix-style paths, for example.

Or try using child_process.spawn without resorting to a 3rd party module or adding platform specific code yourself. Yeesh.

Re: Habits of a Happy Node Hacker

#9

Regarding point 9, if you don't check your `node_modules` into version control don't you run the risk of them disappearing from NPM?

That's a good point, I've never considered the possibility of a package I'm using disappear from NPM. I never check in my node_modules folder and let CI build processes handle all of that.

Re: Habits of a Happy Node Hacker

#10
Until I looked at the actual title of the post, I was a little concerned that somebody had invented a time machine.

It's been changed now, but originally was titled "10 Habits of a Happy Node Hacker (2016)"

Post reply on HN