-
Notifications
You must be signed in to change notification settings - Fork 211
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
issue with v4 and yarn pnp #1090
Comments
Sorry for the incredibly late reply on this. I've been looking into Yarn PnP stuff. I spent the entire day yesterday tracking things through Yarn itself b/c all of its lookups are case sensitive (which is causing me some major headaches on Windows). This error appears to come from the fact that Yarn PnP doesn't really support ESM. They like… kinda have support through the use of Node's loaders feature. It has to be manually registered and in my testing… it just doesn't work right. I'm gonna keep working on it but since PnP completely replaces Node's resolution algorithm and requires runtime patching of internal Node APIs to function at all it's a very, very, brittle feature to support and I've even run into deadlocks if I called the PnP API's |
I did a bunch of work on Yarn PnP stuff a little over a week ago. Which in this case includes loading the CJS build of v4 if Yarn PnP is being used (was really hoping I could only ever load the ESM build for v4 😭) Could you try the latest version of the extension (v0.14.3)? |
it works :D |
awesome 💯 thanks for testing! |
vscode version:
1.96.0-insider
intellisense version:
[email protected]
tailwindcss version:
[email protected]
package manager:
yarn
with pnpoperating system: arch linux
Tailwind config
VS Code settings
Describe your issue
intellisense not working; this is the error in the console:
The text was updated successfully, but these errors were encountered: