Skip to content
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

docs: update vite instructions #713

Merged
merged 1 commit into from
Aug 16, 2024
Merged

docs: update vite instructions #713

merged 1 commit into from
Aug 16, 2024

Conversation

jtidwe11
Copy link
Contributor

❓ Type of change

  • πŸ“– Documentation (updates to the documentation, readme or JSdoc annotations)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ 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)

πŸ“š Description

A pull request in Vite 5.3.0 introduced a change where the tsconfig.json file was separated into three files: tsconfig.json, tsconfig.app.json, and tsconfig.node.json:

vitejs/vite#15913

The compilerOptions change also needs to be propagated to the tsconfig.app.json otherwise the module resolution will fail upon build.

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

If compiler options are only added to just tsconfig.json, module resolution fails for `@/lib/utils` during build.
@sadeghbarati sadeghbarati merged commit 12657da into unovue:dev Aug 16, 2024
1 check passed
sinh117801 added a commit to sinh117801/shadcn-vue that referenced this pull request Aug 17, 2024
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) -->

### πŸ”— Linked issue

<!-- Please ensure there is an open issue and mention its number as unovue#123 -->

### ❓ Type of change

<!-- 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)

### πŸ“š Description

<!-- Describe your changes in detail -->
<!-- Why is this change required? What problem does it solve? -->
<!-- If it resolves an open issue, please link to the issue here. For example "Resolves #1337" -->

### πŸ“Έ Screenshots (if appropriate)

<!-- Add screenshots to help explain the change. -->

### πŸ“ Checklist

<!-- 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.
sinh117801 added a commit to sinh117801/shadcn-vue that referenced this pull request Aug 17, 2024
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 unovue#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 unovue#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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants