-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[✨] Please upgrade @auth/core version in qwik-auth #6122
Comments
Note that as a workaround you can use the PR welcome to set it to a range that works. |
@wmertens, thank you for the suggestions. But I don't understand it. How |
@Nefcanto it works when the versions are compatible. If not, PR welcome :) |
@wmertens, I still don't understand. There is a syntactic problem in |
I opened this issue because after upgrading our codebase (which we do weekly), we realized that when we sign in to our development environment, we get 502 pages behind the authentication. We searched and found https://community.auth0.com/t/502-error-when-hitting-auth-login/72161/10. It seems that they were using an old version. |
@Nefcanto what is the problem in qwik-auth? You don't show the error. And if you have trouble setting up qwik to create a PR, please do open issues for it, we want it to work easily always. |
@Nefcanto if you just want to use a newer version without any code changes to qwik-auth, you can use the npm overrides |
@wmertens, let me test the
|
Better to override for all, so that there's for sure only one instance:
or even
so it uses the version you picked |
@wmertens, thank you so much. Let me test it. I'll come back with the results. |
@wmertens, This is my
And now I get these errors:
And when I went into the |
Looks like the api changed since 0.21, and someone needs to update qwik-auth for it. BTW, none of your dependencies are actual dependencies that your server needs in production, they should all be devDependencies. |
oh and you don't have @auth/core in your devDependencies, so it's not installed maybe? You need to add it |
That's why I asked for this upgrade. The API is changed since And about dependencies, we do need to use axios for our client code. Or Chart.js to render charts. I don't understand how you say that they are not used in production. |
It was there. I removed it. You guided me to use |
This is my new
And this is the error I get:
Just the same as before. And this is the result of
|
Could you offer a minimal reproduction? |
@JerryWu1234, with respect, I think there is no need for an MRE. |
Same issue, I can't use any of the email providers (Resend, Sendgrid) to send a magic link email because |
PRs welcome! Or vice versa, someone adding qwik support into @auth would be even better. |
@wmertens, I wish I could, but I can't. However, in this case I don't think a PR is really required. As far as I remember the API change is very easy and it might only take 10 minutes for one of the members of the Qwik team. I think a better approach could be to give it a try, and if it's time-consuming then waiting for a PR would be a better choice. |
the problem is that I don't use it myself, so it should be done by someone who knows it; also, all contributors are busy on v2 etc. |
@wmertens |
@JerryWu1234 cool! @Nefcanto any pointers for Jerry? |
@JerryWu1234, thank you. Two points:
|
@PatrickJS, not solved yet. I updated the
|
Is your feature request related to a problem?
We use qwik-auth which means that we also have to use @auth/core. But we're stuck. We need newer versions, but we can't go beyond
0.21.0
because we get error.Please upgrade your dependency and fix that bug.
https://github.com/QwikDev/qwik/blob/main/packages/qwik-auth/package.json
Describe the solution you'd like
We would love to be able to keep updated with the newest versions of dependencies, so that we can use their newest features and bug fixes.
Describe alternatives you've considered
There is no alternative in this case. We're stuck.
Additional context
No response
The text was updated successfully, but these errors were encountered: