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
When selecting a suggested bundler to build a library, the expected configuration is not generated.
The build task is missing, making it impossible to build the library.
Broken Styles in Generated Code:
When selecting Tailwind CSS during setup, the generated components do not use Tailwind classes as expected.
Instead, the generated code references a missing CSS module named "styles", leading to broken styles
Expected Behavior
A proper build configuration should be generated for buildable libraries, and the build task should be available. Or CLI should prevent users from selecting a bundler to avoid misleading users.
When Tailwind is selected, the generated components should correctly use Tailwind classes instead of a non-existent CSS module.
✔ Which stylesheet format would you like to use? · tailwind
✔ Which bundler would you like to use to build the library? Choose 'none' to skip build setup. · vite
✔ Which linter would you like to use? · eslint
✔ What unit test runner should be used? · jest
I'm facing same sort of issue on macOS. In my current project, I am using a prior version of Nx before Project Crystal, and I'm currently testing on a clean workspace setup how to get buildable libraries going, and the whole setup is broken. If I try to generate a library from the @nx/next generator, it doesn't create the library in a way that makes it immediately buildable. There was no "build" target being inferred.
Current Behavior
When using
@nx/next
, the following issues occur:Expected Behavior
GitHub Repo
No response
Steps to Reproduce
execute step by step:
Options to select:
✔ Which stylesheet format would you like to use? · tailwind
✔ Which bundler would you like to use to build the library? Choose 'none' to skip build setup. · vite
✔ Which linter would you like to use? · eslint
✔ What unit test runner should be used? · jest
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: