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
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