Closed redabacha closed 1 month ago
ah nevermind i figured it out, i just had the vite resolve.alias in the config setup incorrectly. however i did notice that the tailwind.css
file was actually being parsed by deno info
successfully (because it happened to also be valid js syntax) which in turn was giving the responsibility of loading it to the plugin instead of vite.
when importing a css file using a resolver alias, i encounter an error like this:
this can be reproduced from this branch here after running
deno install
anddeno task dev
ordeno task build
.i notice that if i remove the null bytes (
\0
) from the ids by editing the plugin (specifically theisDenoSpecifier
andtoDenoSpecifier
functions) in my node_modules folder, the builds on both dev and prod will work but there will be a flash of unstyled content in dev which isn't ideal.