If you're pulling from npm, you should be getting the already built version. And to use it, you can use a regular function expression instead of the fat-arrow syntax. I'm not sure what requirement you're referring to.
The project itself is using wp/babel, but the output is usable, and what's in npm that you can use without it. All the dependencies in package.json are dev dependencies, if you do a prod install, it won't even download them.
That said, I can't think if the last project I started that wasn't using babel.
Man, promises + async/await is so much cleaner...
async function doStuffInSeries() {
var r1 = await doThing1();
var r2 = await doThing2();
if (r2) {
await doThing3();
}
return {r1,r2};
}
Much easier to follow than the module in question.. also not sure what it really offers over the `async` package, beyond somewhat smaller footprint.
Well, it's an improvement over a few months ago... though, I'm curious if they're still limited to two layers on the routers for deferring a route/root to a child.
Also, it's kind of disturbing to see significant changes this far along. I still don't care for ng (2 is better than 1), just the same, I find react components more intuitive.
Regarding invalidating JWT...
Have client keep initial credentials in memory, use JWT for all transactions, have issued JWT valid for N minutes, after JWT expires, require client to get a new JWT... allow expired JWT for insensitive areas, but require reauth for sensitive ones, unless same session in the browser. By having a much shorter JWT lifecycle, you can skip the revocation server.
npm scripts have been there from the start. I've been using them as my primary entry for some while. Even with grunt/gulp, as you can simply use the version defined in package.json with a project instead of relying on a global, potentially incompatible version.
Beyond this, in general, it's just easier to work with. If you need more, a ./scripts/ directory with one or more scripts started via npm that use shelljs works very well.
Yeah, I'm definitely interested in seeing React-Native-alike options make it... IIRC there's something for the newer windows bits, but haven't looked into it, and it isn't cross-platform.
Although ESLint itself is pretty much a clean slate by default, the AirBnB config[1] is a decent starting point... and although I don't agree with everything, it's pretty understandable as a base.
[1] https://www.npmjs.com/package/eslint-config-airbnb-base
While most of the controls really don't do too much over direct HTML, I do think the notifications look decent, especially compared to the typical toast style notifications.
Man, promises + async/await is so much cleaner... async function doStuffInSeries() { var r1 = await doThing1(); var r2 = await doThing2(); if (r2) { await doThing3(); } return {r1,r2}; } Much easier to follow than the module in question.. also not sure what it really offers over the `async` package, beyond somewhat smaller footprint.