I think a lot of people fear webpack because of opinions from versions <3. Now, with version 4+ there is literally even zero config.
Slap your js into src/index.js, do your thing, run npx webpack-cli and it will spit out results to dist/main.js (afair).
This is the most basic webpack usage. No babel, no loaders, no preprocessors, just resolving, bundling, and with optimizations if used with --mode=production.
I must say, i jumped on the webpack wagon pretty early (somewhere in 1.x), learning curve was steep, i still sometimes feel its magic (especially when it comes to cacheGroups thingy ;)), but this is hands down, the best thing i learned for frontend development (im performance oriented).
Hey Pawel, I actually started my Webpack experience with version 4 and was still afraid ;)
The learning curve wasn't too steep though.
And yes, the boost to my frontend knowledge thanks to Webpack was amazing!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think a lot of people fear webpack because of opinions from versions <3. Now, with version 4+ there is literally even zero config.
Slap your js into
src/index.js
, do your thing, runnpx webpack-cli
and it will spit out results todist/main.js
(afair).This is the most basic webpack usage. No babel, no loaders, no preprocessors, just resolving, bundling, and with optimizations if used with
--mode=production
.I must say, i jumped on the webpack wagon pretty early (somewhere in 1.x), learning curve was steep, i still sometimes feel its magic (especially when it comes to cacheGroups thingy ;)), but this is hands down, the best thing i learned for frontend development (im performance oriented).
Hey Pawel, I actually started my Webpack experience with version 4 and was still afraid ;)
The learning curve wasn't too steep though.
And yes, the boost to my frontend knowledge thanks to Webpack was amazing!