This was such an amazing tutorial. You should give tutorials on how to write effective tutorials. Seriously...so many people want to skip ahead to complicated workflows and to just 'assume away' the basics of webpack (or any other technology). (As just one of many examples, I love how you took the time to explain how the path object in Node works). It's great when the underlying technology can be separated from its environment so that you can see how it works without other dependencies and adjacent applications muddying the waters. Great job; keep up the good work!
+Patrick Ryll Dude legit made my day haha. Thanks so much I really appreciate it! These vids came out of a frustration just like yours. I often find people making videos that basically just tell you what to type. Which often leaves me with more questions than I had before I watched. Webpack is awesome but it's def complicated. But it has to be! It's solving a complex problem. Everyday I learn a little more about it and I am happy to share what I've learned with others. Thanks for taking the time to watch ✌🏻️
This series of videos was a godsend and came at just the right time! Webpack totally makes sense now ... it was hard playing catch up with webpack as opposed to following along with the incremental evolutionary changes over time. You did a masterful job of logically piecing webpack back together, step by step, with explanations and a rationale for each configuration section. Many thanks!!
Thank you so much for the kind words and for watching! I'm glad you found these videos so helpful, it inspires me to make more! ....which I really should be getting to any day now lol Thanks again!
Dude, I have paid for tutorials and they were great. But watching these is when I got Webpack. Maybe it was a mix of everything, but you explained things so well. Thank you!
Awesome videos. Thanks for the webpack series. You mentioned about adding CSS to your webpack config... I tried this and even after looking at the docs couldn't figure out what was up... Would love to see a video on that as well. Thanks!
Could this have an effect on using the console when hitting break points? I am seeing that I do not have access to watchers and property values in the console with the current configurations.
If you run webpack-dev-server or webpack, it will run with the same devtool, yeah? Is there a way to separate which source map you use, depending on the script you choose? Or should I just always use a production one?
The nice thing about the config is that it's just a javascript object, so yea a lot of people will use environment variables to toggle out different settings. I wanted to make a video about a production build setup but never got around to it. However there's a lot of info out there about making production builds for webpack so check those out!
Thanks for the quick reply! I was actually thinking about how to pass that in as a variable through the CLI for my npm start script to override the "production supported" source map, but I just hadn't figured out how to do that yet. I'll look around a bit more!
So I must have been tired, but I didn't see this in the docs the first time through, but here's my answer; in case anyone else has my same question. webpack.js.org/api/cli/
These tutorials really take the 'magic' out of webpack. Thank you for explaining it so clearly.
I hava seen tons of videos and blogs about webpack, but your tutorial definitely is the clearest one I ever seen, Thank you so much!!!
Thank you for this series. It was awesome. The mystery of the webpack.config.js is no more for me.
This was such an amazing tutorial. You should give tutorials on how to write effective tutorials. Seriously...so many people want to skip ahead to complicated workflows and to just 'assume away' the basics of webpack (or any other technology). (As just one of many examples, I love how you took the time to explain how the path object in Node works). It's great when the underlying technology can be separated from its environment so that you can see how it works without other dependencies and adjacent applications muddying the waters. Great job; keep up the good work!
+Patrick Ryll Dude legit made my day haha. Thanks so much I really appreciate it!
These vids came out of a frustration just like yours. I often find people making videos that basically just tell you what to type. Which often leaves me with more questions than I had before I watched. Webpack is awesome but it's def complicated. But it has to be! It's solving a complex problem. Everyday I learn a little more about it and I am happy to share what I've learned with others. Thanks for taking the time to watch ✌🏻️
This series of videos was a godsend and came at just the right time! Webpack totally makes sense now ... it was hard playing catch up with webpack as opposed to following along with the incremental evolutionary changes over time. You did a masterful job of logically piecing webpack back together, step by step, with explanations and a rationale for each configuration section. Many thanks!!
Thank you so much for the kind words and for watching!
I'm glad you found these videos so helpful, it inspires me to make more!
....which I really should be getting to any day now lol
Thanks again!
This is by far the best tutorial that i found on webpack. Thanks a lot.
Wow, thanks a lot!
The amount of time this save me alone (not to mention the level of clarity) is worth at least a couple of beer. Looking forward to the next series 👍
+Tyler Reitz 🍻 cheers!
Dude, I have paid for tutorials and they were great. But watching these is when I got Webpack. Maybe it was a mix of everything, but you explained things so well. Thank you!
Wow thanks so much, I truly appreciate the kind words and I'm glad I could help you out!
Happy coding ✌️
Man, you are so much better than those I won't name explicitly have like 200k+ followers with their useless tuts. Thank you.
Wow, that's very nice of you to say, thanks so much! I'm glad you found the videos useful.
Awesome videos. Thanks for the webpack series. You mentioned about adding CSS to your webpack config... I tried this and even after looking at the docs couldn't figure out what was up... Would love to see a video on that as well. Thanks!
Hey thanks for watching! It's been in the works for some time now but I've been busy/lazy lol. Hopefully I will have them done sometime in February
Thank you so much for these tutorials! Clearly explained and all. Super nice!
This series is awesome! Thank you!
Could this have an effect on using the console when hitting break points? I am seeing that I do not have access to watchers and property values in the console with the current configurations.
i have to problem with the webpack 3. this methode is not working for me
If you run webpack-dev-server or webpack, it will run with the same devtool, yeah? Is there a way to separate which source map you use, depending on the script you choose? Or should I just always use a production one?
The nice thing about the config is that it's just a javascript object, so yea a lot of people will use environment variables to toggle out different settings. I wanted to make a video about a production build setup but never got around to it. However there's a lot of info out there about making production builds for webpack so check those out!
Thanks for the quick reply! I was actually thinking about how to pass that in as a variable through the CLI for my npm start script to override the "production supported" source map, but I just hadn't figured out how to do that yet. I'll look around a bit more!
So I must have been tired, but I didn't see this in the docs the first time through, but here's my answer; in case anyone else has my same question.
webpack.js.org/api/cli/
subscribed, you are awesome!
cool,thanks
yes yes good
devtool: 'inline-source-map',