npm: update express to 5.1 #8531
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ref #8529
This gives me headaches. The core issue is there are no longer those flexible regex routes. Rather a more strict system, i.e.
path-to-regexp
updated. One place where I'm stuck is the proxy setup for projects. The idea I have is to create a small middleware, which checks if the supposed project ID is actually an UUID – otherwise to pass on internally to the next route. router level middleware This also implies that the "string-regex" passed toinitUpgrade
needs to be different than the more general path for the route.What I got to work is e.g. the index page, loading frontend, redirecting to specific frontend pages, etc. The websocket connection doesn't work though. Some detail must be off.
Also, just while running the dev server, I get weird sudden crashes like that:
What I haven't even started to look into is the api/v2 endpoint: