-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to resolve preset from published config #412
Comments
Hey @JeffBeltran. Is |
hey thanks @bradlc, "main": "./dist/bowtie.umd.js",
"module": "./dist/bowtie.es.js",
"exports": {
".": {
"import": "./dist/bowtie.es.js",
"require": "./dist/bowtie.umd.js"
},
"./config": "./dist/config/index.js"
}, and just to be more clear // this works for both this extension and tailwind config
presets: [require("./node_modules/@homevalet/bowtie/dist/config")]
// this only works for the tailwind config, the extension gives the above error
presets: [require("@homevalet/bowtie/config")],
// this doesn't work for any of them
presets: [require("@homevalet/bowtie/dist/config")] if it would help i'll throw together a public example |
Thank you @JeffBeltran - I have the same issue, and your |
Thanks for the details @JeffBeltran! This should be fixed in |
Cheers @bradlc just tested this out and can confirm this is now resolved resolved |
I ran into the same issue as #333, However, im trying to reference a published preset (Github package). Tailwind has no issues with this, but in vscode this extension crashes
but the extension throws the following error
this could 100% be on me with how i published the module, but at this point this extension is the only thing not working.
if it helps, i can fix the issue with the above error by directly referencing the module via
so not a blocking issue but would be nice to see if it's something i could do on my end.
Cheers and thanks for this great extension
The text was updated successfully, but these errors were encountered: