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.

0 reposts0 likes

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...

The work consists of deleting the rule and then working my way through hundreds of now unresolved import errors and updating `import w from "z"` to `import w from "x/y/z"`.

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.