Skip to content
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

yarn has tailwindcss issue, npm doesn't #9

Open
Bersaelor opened this issue Feb 18, 2023 · 0 comments
Open

yarn has tailwindcss issue, npm doesn't #9

Bersaelor opened this issue Feb 18, 2023 · 0 comments

Comments

@Bersaelor
Copy link

When checking out your project I first tried yarn:

❯ yarn
yarn install v1.22.19
info No lockfile found.
[1/4] πŸ”  Resolving packages...
warning @crxjs/vite-plugin > magic-string > [email protected]: Please use @jridgewell/sourcemap-codec instead
[2/4] 🚚  Fetching packages...
[3/4] πŸ”—  Linking dependencies...
warning " > [email protected]" has unmet peer dependency "@babel/core@^7.0.0".
warning "babel-preset-solid > [email protected]" has unmet peer dependency "@babel/core@^7.20.12".
warning "babel-preset-solid > babel-plugin-jsx-dom-expressions > @babel/[email protected]" has unmet peer dependency "@babel/core@^7.0.0-0".
warning " > [email protected]" has unmet peer dependency "tailwindcss@^3.2.2".
warning " > [email protected]" has unmet peer dependency "webpack@^5.0.0".
[4/4] πŸ”¨  Building fresh packages...
success Saved lockfile.
✨  Done in 73.83s.
✨  Done in 73.83s.
❯ yarn dev
yarn run v1.22.19
$ vite build -w
vite v3.2.4 building for production...

watching for file changes...

build started...
βœ“ 20 modules transformed.
[vite:css] Failed to load PostCSS config (searchPath: ../chromeextension): [Error] Loading PostCSS Plugin failed: Cannot find module 'tailwindcss'
Require stack:
- ...chromeextension/postcss.config.cjs

(@/...chromeextension/postcss.config.cjs)
Error: Loading PostCSS Plugin failed: Cannot find module 'tailwindcss'
Require stack:
- ...chromeextension/postcss.config.cj

and it didn't work.
With npm it seemed to work fine. I use nvm, so it correctly detected the projects .nvmrc to use v16.16.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant