Replies: 1 comment 1 reply
-
|
Is this repo a reproduction of the issue? https://github.com/yurai-git/ve-test |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm developing a Nuxt module using vanilla-extract. When running the playground, I encounter a
No CSS for fileerror.It appears that the Vite plugin is incorrectly prepending the project root to an already absolute path, resulting in a double resolved path like:
C:/.../playground/C:/.../src/runtime/composables/hello-world.css.tsReproduce
Create Nuxt module project
Open the project folder in any IDE
Install vanilla-extract and the required bundler
Set up a component, composable, and main entry point
src/module.ts:src/runtime/composables/hello-world.css.ts:src/runtime/components/hello-world.vue:Import this module and the component in playground
playground/nuxt.config.ts:playground/app.vue:Start and open the development server
Expected behavior
The page should renders
<div>Hello, world!</div>with red text.Observed behavior
Vite throws the following error:
It appears the file path is being doubly resolved or incorrectly concatenated, resulting in an invalid absolute path.
Does anyone know how to correctly configure the path resolution for vanilla-extract within a Nuxt module context?
Any help or guidance would be greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions