You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using vanilla extract, which imports .ts files called foo.css.ts
So in application code, it ends up looking like an asset import and triggers that pipeline.
import{vanillaExtractClass}from'./file.css';
Then if I run packemon against a library that uses this:
ENOENT: no such file or directory, copyfile
'/Users/alex/project/packages/@project/ui/src/Badge.css' ->'/Users/alex/project/packages/@project/ui/assets/Badge-70d967 b6.css'
Presumably because there is no .css file. It's referring to a .css.ts file and the normal import behavior is what i'm after.
I don't actually need this feature, so it'd be fine if I could somehow disable it, or minimally disable it for .css files. My guess is there's some way to inject a rollup config override, but I haven't found the exact right magic.
The text was updated successfully, but these errors were encountered:
I am using vanilla extract, which imports
.ts
files calledfoo.css.ts
So in application code, it ends up looking like an asset import and triggers that pipeline.
Then if I run packemon against a library that uses this:
Presumably because there is no
.css
file. It's referring to a.css.ts
file and the normal import behavior is what i'm after.I don't actually need this feature, so it'd be fine if I could somehow disable it, or minimally disable it for
.css
files. My guess is there's some way to inject a rollup config override, but I haven't found the exact right magic.The text was updated successfully, but these errors were encountered: