Hi,
There were a few issues with using the current installation command:
The --typescript option is not supported.
When the --no-interaction flag is included, it cannot choose the default testing framework, which results in an error.
This PR will remove the two options, --typescript and --no-interaction.
Screenshots of the errors are listed below:
Thank you :)
* docs(table): add `DataTableReactive` example and tanstack docs
* chore: build:registry
* docs: refrase
* docs(data-table): update `defineModel`
* fix(data-table): change `reactive` data to `shallowRef`
* docs(data-table): add info about `ref` and `shallowRef`
* feat(app): #537 auto install the module
This pull request is intended to install the module during the installation of the module
Closes: #537
* docs: update Nuxt dark mode
---------
Co-authored-by: selemondev-triply <selemon@triply.co>
* feat(docs): add vertical Tabs example and components for account/password management
* fix(TabsTrigger): wrap slot content in a span with truncate class for better text handling
* chore: build:registry
If compiler options are only added to just tsconfig.json, module resolution fails for `@/lib/utils` during build.
<!---☝️ PR title should follow conventional commits (https://conventionalcommits.org) -->
<!-- Please ensure there is an open issue and mention its number as #123 -->
<!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply. -->
- [ ] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
- [ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
- [x] 👌 Enhancement (improving an existing functionality like performance)
- [ ] ✨ New feature (a non-breaking change that adds functionality)
- [ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
- [ ] ⚠️ Breaking change (fix or feature that would cause existing functionality to change)
The change is mean to allow event type to support `values: z.infer<typeof schema>`, not only `values: Record<string, any>`
Resolves#716
<!-- Add screenshots to help explain the change. -->
<!-- Put an `x` in all the boxes that apply. -->
<!-- If your change requires a documentation PR, please link it appropriately -->
<!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [x] I have linked an issue or discussion.
- [ ] I have updated the documentation accordingly.
