4 ms·
I'm not even a JS dev, I support the CI pipelines and Docker images and whatnot. It's something else every week. When I get it to work eventually, it's brittle
by avhception 1y ago
I'm not even a JS dev, I support the CI pipelines and Docker images and whatnot. It's something else every week. When I get it to work eventually, it's brittle as hell. I just want the madness to stop. I don't even care any more.
- c-hendricks 1y agoAnecdotal, but I switched our webpack configs with vote a few years ago and haven't had to touch it since. Didn't have to touch the webpack stuff either. Perhaps the issues you're having are due to something else?
- brightball 1y agoTake a look at Rails 7+. They shifted to just using import maps and abandoned the build step entirely. Simplifies everything.
- manniL 1y agoThey also abandoned performance!
- brightball 1y agoAre there any negative performance stories that came from the move? I can't imagine any negatives outside of "1st load"?
- Muromec 1y agoIf you support the CI pipelines, you can put some conventions that you expect to run npm ci, npm build and then npm unit-tests-run and you don't care what they use as long as it returns without errors and puts the deployable artifact in ./dist/public/ or whereever you expect it. If you are bold enough you can ask to write makefiles too -- let them have it. Why should it even be your problem.