3 ms·

I am not node developer, but I don't think it solves the problems it is supposed to. Serving pages rendered with node via webserver (nginx, apache) is not the

I am not node developer, but I don't think it solves the problems it is supposed to. Serving pages rendered with node via webserver (nginx, apache) is not the most pleasant experience compared to e.g. python + wsgi npm packages are not packages. It is simply a dependency definition + repository. Pull in package from npm and it is nowhere near usable until you figure out where it actually puts the files you care. You only know it's somewhere in `node_pacakges/`. Compare to e.g. gulp or python pip. You just pull in a package and it's usable.

moron4hire 11y ago
You are right, you're not a node developer.
honua 11y ago
> Pull in package from npm and it is nowhere near usable until you figure out where it actually puts the files you care. You only know it's somewhere in `node_pacakges/`. Not usable for what? All you need to do is `npm install package` then in your project `const package = require('package')` and it's usable. Also, it's `node_modules`, and gulp itself is a task runner for... Node, so I don't understand your point there.