Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Is it intentional that maxAge is flagged as deprecated in @types/jsonwebtoken

Open
#779 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale

Research direction

Inspect the linked DefinitelyTyped types/jsonwebtoken/index.d.ts lines 86-90, then compare the maxAge option with this repository's code and README, where no deprecation warning is reported. Done means establishing whether the deprecation is intentional and documenting the conclusion or submitting the corresponding DefinitelyTyped change.

Written by the indexing model from the issue text.

Description

Description

https://github.com/DefinitelyTyped/DefinitelyTyped/blob/73b90cedc748d3da3cb203d7dd6e7a6f806fdc17/types/jsonwebtoken/index.d.ts#L86-L90

I don't see any deprecation warning in code or readme in this repo, is it intentional? From git blame, it seems it was added by @samuelhorwitz 5 years ago.

Should I send a PR to DefinitelyTyped to remove it and change the type to number | string?

Reproduction
Environment
Dominant language
JavaScript
Stars
18.2k
Forks
1.3k
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from auth0/node-jsonwebtoken

All issues in auth0/node-jsonwebtoken

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.