-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[bug] :Error: Cannot read properties of undefined (reading 'resolvedPaths') #6527
Comments
(I am hosting my own shadcn registry) A lot of my users are asking me about this. Would it be possible for shadcn CLI to add the missing aliases automatically if they're missing? |
This worked for me when i encountered this error in the past day or so. |
This worked for me too - is there a place change was announced? |
Found this thread from this post - #6509 Adding the 3 missing aliases fixed it for me. I was unaware a change was made that would require them. Glad to find the fix. |
Today, I faced this error. When I checked the ShadCN GitHub repository, I found the solution. The issue occurred because I missed adding ui, lib, and hook in the components.json file. After adding them, the problem was resolved. |
Thanks that worked but can someone explain why the error happened in the first place, previously, we didn't have to do this. |
Works now, after wasting so much time cleaning and reinstalling packages unsure about the issue. |
adding "components": "@/components" in aliases, worked for me, thankss |
- Add shadcn/ui's Badge component - Add basic styling to tournament header - Fix aliasing issue with shadcn/ui 2.3.0 (shadcn-ui/ui#6527)
i wasted so much time, finally fixed it. Thanks. |
…d hooks in components.json (shadcn-ui/ui#6527 (comment))
me too worked, thanks so much |
Thank you it worked. |
thank you, it works! |
works |
Works for me in components.json
|
this works for me also |
Thanks a lot. It works flawlessly. |
Fixed in new |
If you're seeing the error message, make sure you have aliases defined for
components
,utils
,ui
,lib
andhooks
in yourcomponents.json
.Thanks @MatiasSommer for helping me debug this.
The text was updated successfully, but these errors were encountered: