Me: Why did you exit the build?
Webpack (W): Build exited with code 2 - Eslint error at 2:1 in *filename*.scss 'Expected 2 line indent'
Me: internally *ARE YOU KIDDING ME?!?!?!? YOU FAILED OVER AN ESLINT STYLING!!!* *curses out original dev profusely under breath while fixing styling*

@bigus-dickus The build pipeline is getting scrapped and rebuilt. It's not worth the time to change the current webpack config due to this. For now I'm just going to rant about it until I finish the replacement.

why the fuck people are now putting linters into build processes? wtf smh

@mishaor the best part is that right after that the code gets minified and obfuscated. So all the linting rules get tossed out the window anyway in the deployed code. 1 of the many reasons I'm trashing it and writing new build scripts.

@bigus-dickus it's done in parallel kind of. The css, HTML (handlebars), and js are done in parallel. It Lints, then precompiles, then minifies/obfuscates for production with babel piped in there in places. It makes no logical sense but it sort of works. The config file is like 400 lines long. It's one big mess that hangs together by a thread. The whole front end is written that way. Pulled on a thread too hard once and found out the hard way how messy the original dev was with the app architecture.