Re:Step-by-step tutorial to build a modern JavaScript stack ...
by Matachines on Saturday October 29, 2016 @04:52PM
(#12826307)
Webpack is weird in that it's lumped with task runners/"Make"-like programs but it actually it's a configurable and hackable version of the browser asset pipeline.
Re:Step-by-step tutorial to build a modern JavaScript stack ...
by vmasto on Saturday October 29, 2016 @02:08PM
(#12825378)
Nit: not sure why you mention const. It does not provide any kind of immutability assurance.
Re:Step-by-step tutorial to build a modern JavaScript stack ...
by k__ on Saturday October 29, 2016 @02:19PM
(#12825458)
I just use const instead of var/let all the time and it prevented me from overriding the variable later, which forced me to write my code a bit more functional then before I used it.
I know that I can still change indirect references or override valueOf() etc.
Re:Step-by-step tutorial to build a modern JavaScript stack ...
by pault on Saturday October 29, 2016 @06:29PM
(#12826817)
You probably know this, but for anyone else reading, the problem is that if you assign an object or array using const, the object/array members are still mutable. If you have a tree structure, you have to recursively Object.freeze the entire tree to get immutability, which AFAIK is basically what immutable.js does for you. I also use const by default, but I find that more often than not my variables are trees and lists.
I wouldn't consider Webpack an alternative to Gulp. Gulp is more generic. But if you use Webpack you can replace to task-runner part with a few scripts.
When using ES6 or TypeScript I'd also consider Immutable to be optional, because of "const" and "Object.assign()/Spread-Operator".
Also, React & Redux can be replaced with 1 thing, when you use a framework that bundles view components and state management.