> TheSmartGuy: listen, IHateForALiving, I know you're a frontend developer, but here in the backend...

Just so we're clear: I'm NOT a frontend developer.

I'm a full stack developer.

I just so happen to always end up working on the frontend because you bunch of handless monkeys wouldn't be able to write a webpack config file if your life depended on it.
It's not you taking care of my inability to work on the backend, it's me being relegated to using only half of my skills because you ugly things refuse to evolve. I could take your job in a breath, I wouldn't trust you with writing a css selector.

What's a webpack config file?

Me, a backend developer.

@atheist makefile, but for the frontend.

It's the grossest simplification ever -webpack can configure the preprocessor, resource loading and caching, rules for different file types and what not... and I have no idea of the shenanigans you can do with a makefile-, but it's basically the tool you use when you want to take some source files and compile them.

I mean. full stack means you do both no?

Do frontend but get paid for fullstack. Win-Win.

@IHateForALiving I know webpack can do stuff like turn scss to css

...but other than that, why do we need it?

isnt any frontend a collection of js css and html that would be served by something like nginx and from there its on the browser to figure it out?

- also another backend dev (i used be full stack when jquery was the latest innovation)

@sleek It would very theoretically work... but only as a PoC.

Webpack will minify your code to avoid sending 10k lines of comments, spaces, very-long-variable names which are useful to humans and useless to a browser; all of that is taking network bandwith and slowing down navigation. Webpack will precompile TS into JS, allowing you to use a whole new language. Webpack will jion all your 10k small files into a single bigger files, to have one single HTTP request instead of clogging your server with 10k handshakes. Webpack will include SOME server-side env variable in your client code (the easiest one: are we in dev or prod?). Webpack will allow you to handle new files, like .vue files (a single file with its individual syntax to have CSS, JS and HTML for an individual component inside an individual file), caching policies, inlining of some images and more.

Looks like you miss some of the political play they do to you.

Me as a backend dev, I can write a webpack config, but I won't ever do it. So the task is yours because I'm too stupid.

As a backend dev I try my best to not do any frontend/web stuff, because I hate it. If you call me dumb that's a small price for me for not doing frontend.