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
why must Verifying framework and import alias?
One of the scenarios I have here is that shadcn/ui in monorepo will only share component files for reuse across projects, it won't be packaged separately, so I don't need a framework, I don't need to import aliases, all I want is to export component files.
This is the monorepo project we created earlier, which is very convenient for sharing shadcn components, but now executing the command line is not successful because of the validation of the framework and the import alias
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
why must Verifying framework and import alias?

One of the scenarios I have here is that shadcn/ui in monorepo will only share component files for reuse across projects, it won't be packaged separately, so I don't need a framework, I don't need to import aliases, all I want is to export component files.
This is the monorepo project we created earlier, which is very convenient for sharing shadcn components, but now executing the command line is not successful because of the validation of the framework and the import alias
Beta Was this translation helpful? Give feedback.
All reactions