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 babel-plugin-relay to v15 #477

Closed
michaelmcneilnet opened this issue Sep 7, 2023 · 6 comments
Closed

Upgrade babel-plugin-relay to v15 #477

michaelmcneilnet opened this issue Sep 7, 2023 · 6 comments

Comments

@michaelmcneilnet
Copy link

babel-plugin-relay v15 is available, but this library depends on v14.

ABC@workspace:. provides babel-plugin-relay@npm:15.0.0 with version 15.0.0, which doesn't satisfy the following requirements:
➤ YN0000: vite-plugin-relay@npm:2.0.0 [f5404] → ^14.1.0 ✘

Is it possible to upgrade this plugin to use v15? Is there another way to remove this warning from yarn?

@artola
Copy link

artola commented Dec 15, 2023

and 16 ?

would not be better in peerDependencies to define ^14.1.0 || ^15 || ^16?

@artola
Copy link

artola commented Dec 19, 2023

@oscartbeaumont do you accept a PR for such change?

@oscartbeaumont
Copy link
Owner

Go for it. I have been meaning to do another Vite Plugin Relay release. Will hopefully do it in the next couple of weeks.

@artola
Copy link

artola commented Dec 19, 2023

Go for it. I have been meaning to do another Vite Plugin Relay release. Will hopefully do it in the next couple of weeks.

The change was already done (6-months ago by @koistya) but he package never released since then:

artola@bcdac05

As soon as you release a package, the problem is gone. Looking forward the NPM release.

@zeroliu
Copy link

zeroliu commented Jan 28, 2024

Hello! I'm glad to see this problem will be solved soon. Is there a timeline for the next release? Thanks for the support!

@tobias-tengler
Copy link
Collaborator

I forgot that I'm also a maintainer on this repository 🙈 I just triggered v2.1.0 which includes the requested change.

FYI @oscartbeaumont: I had to merge #496 & #497 in order to be able to trigger a release.

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

No branches or pull requests

5 participants