-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
New NextJs workspace with tailwind has issues #22475
Comments
Same here |
I notice that's happening in multiple presets |
Had same issue and sad to find |
same here on linux |
Remove the styled component relic |
Same here . Maybe we should optimize these flow:
I found the fast solution is give the comment in file jest.config.ts
|
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Current Behavior
I created new Next.JS workspace using below command.
Issue Description- I chose tailwind but it did not install tailwind and react testing library by default and getting issue to start the app in dev mode. Also observed no scripts added in package.Json by default.
Expected Behavior
Should have installed tailwind and react testing library by default and the app should be working properly.
Also by default commands should be added for dev/build/test/e2e in package.json
GitHub Repo
No response
Steps to Reproduce
Below are choice i made during create workspace
NX Let's create a new workspace [https://nx.dev/getting-started/intro]
✔ Where would you like to create your workspace? · temp
✔ Application name · temp
✔ Would you like to use the App Router (recommended)? · Yes
✔ Would you like to use the src/ directory? · Yes
✔ Test runner to use for end to end (E2E) tests · cypress
✔ Default stylesheet format · tailwind
✔ Do you want Nx Cloud to make your CI fast? · skip
NX Creating your v18.1.2 workspace.
✔ Installing dependencies with npm
✔ Successfully created the workspace: temp.
Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: