https://twitter.com/sindresorhus/status/724259780676575232?l...
https://github.com/ReactiveX/rxjs/blob/a3ec89605a24a6f54e577...
Already people are coming up with new "solutions" to this problem that looks more like Grunt. It's a repetitive circle. Personally I just use Make.
Npm scripts are really just shell scripting, which means all the real progress happens in the unixy Node tools that do the heavy lifting, where it should be. It's a future proof and scalable approach for the vast majority of projects imo.
> Npm scripts are really just shell scripting, which means all the real progress happens in the unixy Node tools that do the heavy lifting, where it should be.
That's fine, but you're missing critical features that Make provides; make won't even rebuild a target if no files have changed.
> That's fine, but you're missing critical features that Make provides; make won't even rebuild a target if no files have changed.
WebPack does this for me too. Also my ava tests don't rerun for files that haven't changed while watching.
Genuinely curious, what scenarios precisely do you find this feature of Make useful?
Also, Make isn't truly cross platform ... and since I sometimes work with Windows devs this would be a problem.
>then you separate your "test" into one for the browser, one for Node, one for CI,
For the love of God why. Don't turn every language into Java.
Plenty of tools will not rebuilt a project if no files have changed, but the dumb, quick and easy way that requires no deendendencies is simply to delete and rebuild.
The fact that this functionality is served so well by a simple dependency shows that you don't need overly complex monolithic tools to accomplish small tasks.
>then you separate your "test" into one for the browser, one for Node, one for CI,
For the love of God why. Don't turn every language into Java
And the Promise/A+ spec is so bare-bones, it is laughable. And the actual issue is that not every module is embracing it yet.
Sure, it will all be fixed. For freeeee :)
Although couched as a criticism this is actually the community fixing itself. The evolution from Grunt > Gulp > npm scripts is movement away from needless complexity towards simplicity. Npm scripts are effectively just Bash commands that build and manage your project, which sometimes employ small, unixy tools written in Node.
This self correction was pretty quick, it happened within a few years.
> Unfortunately, there isn’t any one “standard” (like everything else in Javascript) for implementing or using Promises.
Yes there is. It's called the Promises/A+ spec, and its built into ES6.