Post

Doing the groundwork for an eventual migration from webpack to @vite.dev. If you ever wanted to know where the bodies are buried in your codebase, try unraveling 10 years of webpack configuration and customization.

I'm currently several weeks (part time) into removing our `resolve.modules` rule where we told webpack to look in `a/b/` for our modules... And also `a/b/c/`, and `a/b/c/d`, and `a/b/e`, and `a/b/f`, and...

I'm sure this must have saved the original maintainers whole seconds when writing import statements by hand, but it is now costing me my sanity 10 years later.