chore(deps/backend): bump @nestjs/jwt from 11.0.0 to 12.0.1 in /backend

[dependabot]

Bumps @nestjs/jwt from 11.0.0 to 12.0.1.

Release notes

Sourced from @​nestjs/jwt's releases.

Release 12.0.1

• fix: jsonwebtoken esm imports (05d0075)

Release 12.0.0

What's Changed

@nestjs/jwt is now a native ES module, and the major version is aligned with the Nest 12 release line

ESM migration

The package is published as pure ESM ("type": "module", compiled with NodeNext) behind a proper exports map. The legacy root index.js / index.d.ts / index.ts shims are gone, and deep imports into build internals are no longer resolvable — import from the package root.

// ✅
import { JwtModule, JwtService } from '@nestjs/jwt';
// ❌ no longer resolvable
import { JwtService } from '@​nestjs/jwt/dist/jwt.service';

require(esm) — CommonJS still works

You do not need to convert your app to ESM. Thanks to Node's require(esm) support (Node 20.19+, 22.12+, and all of 24.x), a CommonJS Nest application can keep requiring the package exactly as before:

const { JwtModule, JwtService } = require('@nestjs/jwt');

TypeScript users compiling to CommonJS are unaffected as long as their runtime is on a supported Node version. On older Node releases, require() of this package will throw ERR_REQUIRE_ESM — upgrade Node, or switch the consuming code to import.

jsonwebtoken re-exports

The error classes re-exported from jsonwebtoken (TokenExpiredError, NotBeforeError, JsonWebTokenError) are now re-exported explicitly by name instead of via a star export, so they resolve correctly under ESM interop with the CJS jsonwebtoken package. No import changes are needed on your side:

import { TokenExpiredError } from '@nestjs/jwt';

Upgrading

npm install @nestjs/jwt@12

For most applications this is a drop-in upgrade. Action is only required if you were relying on deep imports into dist/, or are running a Node version older than 20.19 with a CommonJS app.

Release 11.0.2

What's Changed

• fix(deps): update dependency jsonwebtoken to v9.0.3 by @​renovate[bot] in nestjs/jwt#2088

... (truncated)

Commits

• 6c75fa6 chore(): release v12.0.1
• 05d0075 fix: jsonwebtoken esm imports
• 8853ee8 chore(): release v12.0.0
• b8455f2 chore: upgrade to v12
• 542e29e chore(deps): update dependency oxlint to v1.80.0 (#2260)
• ae0d0d7 chore(deps): update nest monorepo to v11.2.3 (#2259)
• af3ad43 chore(deps): update dependency oxlint to v1.79.0 (#2258)
• 53c8fee chore(deps): update dependency vitest to v4.1.11 (#2257)
• 7014c3a Merge pull request #2205 from nestjs/renovate/cimg-node-24.x
• 54a4c5c Merge pull request #2186 from nestjs/chore/esm-migration
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: backend, dependencies. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.