webpack 4.0 to 4.16: Did you know?
I’m still confused about the maxSize option. It garbles all the output file names. Do I have to perform additional steps to load these or link them to an HTML file?
How does the new mode compare with the env parameter?
A hundred million times this. Both deploying to production, staging, and CI are now just free of any node package related bamboozlements.
Nice article and run through the latest developments, especially with the advent of npm5.
Nice one! Should make a mention of where ModuleConcatenationPlugin should be placed in relation to other plugins, specifically, it looks like it must be placed before the CommonsChunkPlugin, else it will fail.
Also, for a flagship functionality to be released and announced without any mention in the documentation is a bit.. well.
Nice, I’ve been waiting for such an implementation. Kudos, sir!
Apologies if my response came out as snark. 🙂 Unfortunately without the bandwidth to watch the video currently, could you elaborate on exactly what APIs are legacy?
Hear, hear! You are absolutely right. “Full-stack developer” is a buzzphrase now devoid of any meaning. In my 20 years of professional web-work I’ve yet to encounter anyone that could rightfully call themselves full-stack.
Think you are missing the point here. It is not about knowing framework or library XYZ. You need to have the core knowledge of how CSS is written, composed, computed, weighted and rendered. Doesn’t matter if you can use XYZ if you still can’t handle the simpler concepts.
“The problem with plain CSS is that it was built in an era where the web consisted of documents.
Well, SVG comes with its own host of issues, language and implementation-wise. I agree it is better for advanced graphics and interactions, but to go turtles all the way down, you could argue that the Canvas API is by far the better option all around and let everyone program their own rendering systems. Which they do, ref Made with Unity and Fuse.