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

fix: Incorrect default export of Vite plugin types under TS's Node16 module resolution #531

Merged
merged 2 commits into from
Dec 24, 2023

Conversation

rschristian
Copy link
Member

@rschristian rschristian commented Dec 24, 2023

https://arethetypeswrong.github.io/?p=%40prefresh%2Fvite%402.4.4

The Options interface is a casualty here that I'm not sure can be avoided -- I did a little searching but it seems it'd be unavoidable. Do use Options? Seems like it'd be a pretty uncommon need.

Copy link

changeset-bot bot commented Dec 24, 2023

🦋 Changeset detected

Latest commit: 36a8c07

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@prefresh/vite Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@rschristian rschristian changed the title fix: Incorrect default export of Vite plugin under Node16 fix: Incorrect default export of Vite plugin types under TS's Node16 module resolution Dec 24, 2023
@@ -0,0 +1,5 @@
---
'@prefresh/vite': patch
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removal of Options (if there isn't a better solution you know of, anyhow) might warrant a minor instead -- not sure how you want to handle it.

@JoviDeCroock JoviDeCroock merged commit 0efb604 into main Dec 24, 2023
1 check passed
@JoviDeCroock JoviDeCroock deleted the fix/vite-types branch December 24, 2023 07:06
@github-actions github-actions bot mentioned this pull request Dec 24, 2023
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