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: override @type/node to ensure consistent types #85

Merged
merged 2 commits into from
Jun 28, 2022

Conversation

haoqunjiang
Copy link
Member

@types/node is actually an implicit peer dependency of Vite.
So I overrode it with the version from the Vite project dependencies.

This fixes the most recent iles CI failure.

`@types/node` is actually an implicit peer dependency of Vite.
So I overrode it with the version from the Vite project dependencies.

This fixes the most recent iles CI failure.
@patak-dev patak-dev merged commit 1267fc6 into vitejs:main Jun 28, 2022
@patak-dev
Copy link
Member

Thanks a lot, Soda! Running vite-ecosystem-ci with this on now: https://github.com/vitejs/vite-ecosystem-ci/actions/runs/2577855796

Looks like @DylanPiercey was having the same issue in Marko

haoqunjiang added a commit to haoqunjiang/vite that referenced this pull request Nov 2, 2022
The built bundle of Vite starts with a reference to `node` types:
https://unpkg.com/browse/[email protected]/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.
patak-dev pushed a commit to vitejs/vite that referenced this pull request Nov 4, 2022
The built bundle of Vite starts with a reference to `node` types:
https://unpkg.com/browse/[email protected]/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.
@haoqunjiang haoqunjiang deleted the fix-iles-type branch January 13, 2023 11:01
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