-
Notifications
You must be signed in to change notification settings - Fork 0
chore: remove shadcn registry and use relative imports #1013
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
base: main
Are you sure you want to change the base?
Conversation
|
Warning: Component files have been updated but no migrations have been added. See https://github.com/yext/visual-editor/blob/main/packages/visual-editor/src/components/migrations/README.md for more information. |
packages/visual-editor/src/components/categories/AdvancedCoreInfoCategory.tsx
Outdated
Show resolved
Hide resolved
packages/visual-editor/src/components/footer/ExpandedFooter.tsx
Outdated
Show resolved
Hide resolved
| "docs:preview": "vitepress preview .", | ||
| "generate-registry": "tsx src/components/registry/build-registry.cts", | ||
| "build-registry-docs": "pnpm run docs:build && pnpm run generate-registry", | ||
| "i18n:insert": "pnpm exec tsx scripts/insertI18n.ts", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you can also get rid of packages/visual-editor/artifacts.json, packages/visual-editor/config.yaml, packages/starter/components.json and the scripts.components entry in packages/starter/package.json
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh wait I guess artifacts and config.yaml power the documentation site too
While the component registry was a neat idea, no one used it in practice. We're also limiting hybrid functionality at this point.