Weird interactions between --user-data-dir, outDir, and web-ext

[aklinker1]

Overview

I'd you use a persistent profile, and change the extension's build directory, web-ext won't update the extension installed in the profile to the new directory.

You have to fully quit Chrome or uninstall and re-run wxt for the extension path to be updated properly.

This leads to weird behaviors like entrypoints not using the latest version after saving a change and the dev server randomly crashing on MacOS after 30 seconds.

Need to pull the latest code from web-ext into my fork, web-ext-run, and investigate what's going on, and if I need to open an issue in web-ext or chrome-launcher.

Related Links

• feat(config): Add outDirTemplate for customizing output directory structure #1074 (comment)
• Improved error message when entrypoint loading fails #1056 (comment)