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

Upgrade nestjs ecosystem to v11 and zod #131

Closed
wants to merge 1 commit into from
Closed

Conversation

darky
Copy link

@darky darky commented Jan 31, 2025

fix #129

@mallowigi
Copy link

I hope he'd merge it soon, I have a fork of it for now but it would be preferable to have the official version

@gitnlsn

This comment was marked as duplicate.

@Manjit2003

This comment was marked as duplicate.

@darky darky changed the title Upgrade nestjs ecosystem and zod Upgrade nestjs ecosystem to v11 and zod Feb 5, 2025
@RavenHursT
Copy link

@BenLorantfy is this a duplicate PR? #133

@RavenHursT
Copy link

@effervescentia @BenLorantfy this one's also waiting for the build to be approved?

How do we know who's got "maintainer" permissions, and who doesn't?

@RavenHursT
Copy link

Does ANYONE have a workaround for this?

I've tried everything.. using --force and --legacy-peer-deps , npm-force-resolutions, even tried pointing the package at the specific commit of this PR, all to no avail.

This is so frustrating when packages end up setting peerDependencies to hard semvers like this 😡

@mallowigi
Copy link

@RavenHursT try with @mallowigi/nestjs-zod for the time being

@RavenHursT
Copy link

Thank you @mallowigi !

@BenLorantfy
Copy link
Owner

When I ran the CI there were some errors, so I created a new PR / branch and fixed them: #134

@BenLorantfy BenLorantfy closed this Feb 7, 2025
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.

Compatibility with nestjs 11
6 participants