chore: bump Node to 24 and replace jsonwebtoken

[phoenix-ru]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This updates Node version used inside project to 24 so that NPM also gets updated to 11.5.1+ to support Trusted Publishing.

As jsonwebtoken is not compatible with Node 24, it got replaced by jose.

The error with jsonwebtoken and Node 24 was (see similar report):

 ERROR  [uncaughtException] includes.bind is not a function                                                                                                                                                                                                        17:13:44

    at .nuxt/dev/index.mjs:2805:34
    at ModuleJob.run (node:internal/modules/esm/module_job:413:25)
    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:660:26)
    at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:101:5)
 ERROR  [request error] [unhandled] [GET] http://localhost:3000/                                                                                                                                                                                                   17:13:58


ℹ Error: Cannot access 'renderer$1' before initialization

📝 Checklist

• I have linked an issue or discussion.
• I have added tests (if possible).
• I have updated the documentation accordingly.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@sidebase/nuxt-auth@1082

commit: 874a4a6

[BracketJohn]

Please consider reducing changes to a minimum.

Besides this: Could not do a propper review - but based on your decision of minimizing changes it's probably good to do the full review in the next iteration only.

[BracketJohn]

Looks good - did you functionally verify that the playground is still in tact? If so, please document it as a comment here and then this is good to merge.

[phoenix-ru]

Looks good - did you functionally verify that the playground is still in tact? If so, please document it as a comment here and then this is good to merge.

Yes, I did when working on it. There's a TypeScript problem due to me haphazardly updating Nuxt, fixing it rn

[BracketJohn]

Glad we caught that.