Replies: 2 comments
-
|
@VincentvD I am facing similar issue starting from cli v. 0.1.45. My workaround solution is to go straight to your package directory (ex. libs/ui) and use the previous version (npx untitedui@0.1.44 add ...) and then just fix the imports to the relative paths. Hope this would be helpful for you |
Beta Was this translation helpful? Give feedback.
-
|
@wjossowski appreciate the workaround! I'm facing a similar issue with the new installer. It makes some assumptions about the project structure that are pretty opinionated and don't suit my project. This was easy enough to get around (pathing-wise) in the old version but the new version flat-out errors out without css files in a "styles" directory relative to where you're running the command. It seems like a step backwards and the docs gloss right over it, other than mentioning css files in a "styles" directory. A more robust solution that works for projects that don't follow the specific setup for Next.JS or whatever that setup is for is required. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Description
I have a turborepo setup with nextjs and tailwindcss/untitledui. All my untitledui components are in a packages/ui folder. My app is in apps/nextapp. Because paths weren't correctly set, I copied the individual component source from untitledui docs in packages/ui. For pro components, I used the CLI to install the component in my app and then manually move it to my packages/ui. What is the correct way to do this instead of my hacky workaround?
I think how it should work is that it should be possible to use the CLI in the packages/ui folder and install/update components there directly. However; I've tried this and I keep getting 'The project does not seem to be configured with Untitled UI Tailwind.'
Any help is appreciated!
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions