Didn't watch the whole video, so not sure if this was mentioned, may come back later today to do that.
While I appreciate all efforts to make publishing for linux desktop better, really should include windows and mac in most deployment strategies if you're going that route, and are able to technically. The sad thing is it does usually wind up costing in one way or another (windows and mac build servers). But the fact is there are *SO* many more windows and mac users out there.
I'll often take it a step further than that... since I tend to break up my actioncreators and reducers by feature and that feature is within a redux subtree, I may
import { SAVE, SAVE_SUCCESS, SAVE_FAIL } from './constants'
but underneath it is likely...
export const SAVE = 'promise:feature/save';
export const SAVE_SUCCESS = 'resolve:feature/save';
export const SAVE_FAIL = 'reject:feature/save';
in this way I can have extensions in redux to handle 'promise:*', 'resolve:*' and 'reject:*' generically, in addition to or before the resolver.
Recently, I started a brand new React project, router v4 was near release, and a few other bits that were new (to me), using Webpack 2 for the first time, and a few other bits... to be honest, it was about as frustrating an experience as I've had in bootstrapping a new project. Now, it's not as frustrating, but it's really the first time I felt *that* frustrated, so I can feel the pain of a lot of others.
That said, I would never want to go back to the old days of manually bundling, or using script runners for bundle/reduce... Or doing manual namespacing in JS to avoid collisions in a large project. Modern ES6 (or node/cjs) modules are much cleaner, and you can take my Babel before browsers support all the current stage-2+ features I use from my cold dead fingers. It'll bee 3-4 years before that really happens. And it will be weird the transition from build/deploy bundling to JS modules from the browser, and HTTP2 server-push. I still prefer the way JS is written today vs any time before.
I use a lot of async functions, and some ES6 classes (sparingly) where needed. There are a lot of great things in writing modern JS. The flip side is evaluating modules in npm, and keeping up with some of the proliferation without falling into the trap before they're ready, or likely to take established roots.
Interesting... reminds me a lot of ASP.Net MVC attribute decorators for controllers... though would be interesting to have some shortcuts, or other defaults (based on naming), but then you may as well replace express.
Aside, two signup forms taking over the screen *before* you see any content.. bad form... I don't mind it quite as much when it detects your cursor heading out of the display, but before you look at anything, really?
The article itself is pretty naive and misleading. Not to mention incomplete, it's most likely clickbait. There's no depth to any of the examples, and mostly just leaves anyone that would be interested wanting without a means to grow.
I'll often take it a step further than that... since I tend to break up my actioncreators and reducers by feature and that feature is within a redux subtree, I may import { SAVE, SAVE_SUCCESS, SAVE_FAIL } from './constants' but underneath it is likely... export const SAVE = 'promise:feature/save'; export const SAVE_SUCCESS = 'resolve:feature/save'; export const SAVE_FAIL = 'reject:feature/save'; in this way I can have extensions in redux to handle 'promise:*', 'resolve:*' and 'reject:*' generically, in addition to or before the resolver.