TypeError: Missing parameter name at 2: https://git.new/pathToRegexpError

Open
#6,724 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
backend

Research direction

Start with the Express 5 migration guide's path syntax section and compare the reported error with the linked path-to-regexp limitations. The issue provides no repository file or test to change; completion would require a clearly identified missing case, addressed upstream or through a documented Express change.

Written by the indexing model from the issue text.

Description

For those who are experiencing this error, please check the migration guide, it documents how to make the necessary changes. If you continue having issues, join this discussion

In the vast majority of cases, it covers all scenarios. We know there are limitations, which are planned to be addressed in future versions of path-to-regexp (path-negation, parameter customization). Once there is an update in path-to-regexp, you will only need to update your package-lock.json. If you feel that a functionality is missing that we haven’t considered, please open an issue in path-to-regexp, Otherwise, just follow the migration guide

Dominant language
JavaScript
Stars
69.7k
Forks
25.6k
Avg merge
2d 9h
Merged PRs (30d)
4

Getting set up

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 expressjs/express

All issues in expressjs/express

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.