Aaron

This is a known issue. I don't think there was a GitHub issue open for it though, so thanks for opening one. I don't plan on implementing this feature for...

Feel free to keep it open 👍

Hmm, interesting. Are you letting the plugin open the browser and install the extension, or are you skipping that and loading the unpacked directory manually? Make sure you're loading the...

WSL has known issues with letting the extension open the browser.  Since the plugin is running in WSL, it will pass `/c/user/path/to/project\dist` to...

Edit: Not sure how I missed this in my initial search a while back, but there's a package called [`is-wsl`](https://www.npmjs.com/package/is-wsl) that we could use. Then we might just need to...

@mklueh I did not know you could run chromium from inside WSL... interesting. If you want to debug it further, can you add logs inside the plugin? Search for `const...

Huh, weird. I think I'm just gonna have to install windows and do some debugging. Does it happen on the vanilla template? And you're using Ubuntu for WSL2?

Work around: import your CSS file into the JS entry point, then remove it from your manifest, and it will be included automatically in your `dist/manifest.json`. ```js // content-script.js import...

Thanks for the repro, I'll get it fixed when I have some free time

@DeKleineKobini Ok, I've looked into this and have a solution. It will change the output directory structure, so I'm not going to include the fix until the next major release...