Skip to content

fix(types): use types from fastify instead of fastify/types/schema to avoid node resolution errors#172

Draft
marcalexiei wants to merge 2 commits intoturkerdev:mainfrom
marcalexiei:fix-resolution
Draft

fix(types): use types from fastify instead of fastify/types/schema to avoid node resolution errors#172
marcalexiei wants to merge 2 commits intoturkerdev:mainfrom
marcalexiei:fix-resolution

Conversation

@marcalexiei
Copy link
Copy Markdown
Contributor

@marcalexiei marcalexiei commented Jun 15, 2025

Comment thread package.json
"@types/node": "^22.15.30",
"@vitest/coverage-v8": "^3.2.2",
"fastify": "^5.3.3",
"fastify": "^5.4.1",
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

peerDependency also needs to be bumped

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I was hesitant to bump the peerDependency for the following reason:
Currently, it specifies fastify ^5, and updating it would require a major version bump.
Since this change only affects TypeScript types and doesn't involve any runtime fixes I felt it wasn't worth triggering a major release for it.

No problem changing it though!

@marcalexiei
Copy link
Copy Markdown
Contributor Author

Still waiting on fastify update.
I just wanted to resolve the conflicts 😅

@dancallaghan
Copy link
Copy Markdown

It looks like that PR has been merged and released :)

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.

v5: error in fastify/types/schema imports when using node resolution

3 participants