You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Qwik's useNavigate function is used to go to pages. The Link component uses it under the hood.
When navigating to a page that imports plugin@auth it crashes
SyntaxError: The requested module '/node_modules/cookie/index.js?v=da1814f6' does not provide an export named 'parse' (at jwt.js?v=da1814f6:42:10)
This bug only effects navigating to pages. The functionality of the plugin is uneffected.
This bug presists even if you're not using the jwt session strategy
How to reproduce
git clone https://github.com/ShererJohn/qwiklab.git
cd ./qwiklab
npm i
next add these env variables
AUTH_SECRET=
AUTH_GOOGLE_ID=
AUTH_GOOGLE_SECRET=
You can change the provider if you want.
Then run npm run dev, open the index page, and then click the link named "Problem link"
Expected behavior
The Link component is supposed to go to the linked page.
The text was updated successfully, but these errors were encountered:
ShererJohn
added
bug
Something isn't working
triage
Unseen or unconfirmed by a maintainer yet. Provide extra information in the meantime.
labels
Nov 20, 2024
ShererJohn
changed the title
Qwik's Link component breaks when linking to a page that uses the auth plugin
Qwikcity's useNavigate function breaks when navigating to a page that uses the auth plugin
Nov 21, 2024
ShererJohn
changed the title
Qwikcity's useNavigate function breaks when navigating to a page that uses the auth plugin
Qwik-city's useNavigate function breaks when navigating to a page that uses the auth plugin
Nov 21, 2024
Environment
Reproduction URL
https://github.com/ShererJohn/qwiklab
Describe the issue
Qwik's
useNavigate
function is used to go to pages. TheLink
component uses it under the hood.When navigating to a page that imports
plugin@auth
it crashesThis bug only effects navigating to pages. The functionality of the plugin is uneffected.
This bug presists even if you're not using the jwt session strategy
How to reproduce
next add these env variables
You can change the provider if you want.
Then run
npm run dev
, open the index page, and then click the link named "Problem link"Expected behavior
The Link component is supposed to go to the linked page.
The text was updated successfully, but these errors were encountered: