CSS Module files not resolved in production build for components rendered as an island #243
Comments
I tried to reproduce but there are dependency resolution issues in that repo unrelated to slinkity. |
Hey @insanity54, thanks for looking into this! Did you check out the branch I linked to? It shouldn't have Lanyon in the dependencies at all afaik. If so, I'll take a look to see what's up! |
@nickrttn you are correct. That's my mistake, I accidentally checked out your main branch. Thanks for the clarification. I got your site built and I'm seeing the same error/warning(?).
I used
There are 404s mixed in with the 200s. Some css, svg, and png files are failing to load because there is no Looking at debug output from the 11ty build (
vite is transforming it as well.
The problem remains that I don't see any of the transformed css from Container.module.css in the |
Yes, this is a pretty strange result! Might be something in module resolution for islands. I'll see if I can figure it out. |
Describe the bug
For components rendered as an island in a template, any CSS Modules files are not being resolved by Vite during a production build with errors like
/src/_islands/Container.module.css doesn't exist at build time, it will remain unchanged to be resolved at runtime
To Reproduce
Steps to reproduce the behavior:
npm install
npm run build
Expected behavior
Module resolution to work as expected in all cases.
The text was updated successfully, but these errors were encountered: