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

[pull] main from vitejs:main #54

Merged
merged 1,290 commits into from
Nov 8, 2022
Merged

[pull] main from vitejs:main #54

merged 1,290 commits into from
Nov 8, 2022

Conversation

pull[bot]
Copy link

@pull pull bot commented Feb 12, 2022

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

@pull pull bot added the ⤵️ pull label Feb 12, 2022
bluwy and others added 29 commits August 21, 2022 19:26
Co-authored-by: 翠 / green <green@sapphi.red>
sapphi-red and others added 29 commits November 1, 2022 10:01
Co-authored-by: frank <frank@hebingjundeMacBook-Pro.local>
The built bundle of Vite starts with a reference to `node` types:
https://unpkg.com/browse/vite@3.2.2/dist/node/index.d.ts

This means those who depend on Vite type definitions should install
`@types/node` in their projects to successfully do type-checking.
In that sense, `@types/node` is an optional peer dependency of Vite.

After this being fixed, we should revert vitejs/vite-ecosystem-ci#85 because not explicitly depending on
`@types/node` *should* be erroneous. The ecosystem CI shouldn't cover
that error for downstream packages.
Co-authored-by: bluwy <bjornlu.dev@gmail.com>
@pull pull bot merged commit d5fe92c into wxsms:main Nov 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.