Revert "deps: manual upgrade to express 5.1.0" #1681
Merged
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.
Reverts #1626
It appears that the Electron build uses an interesting system in which the requests from the client to the server and intercepted in order not to be served over HTTP (for performance reasons).
Unfortunately, this PR breaks the Electron run entirely, most likely due to the API change of Express 5.
Was almost able to solve it on my side, but I couldn't get past the CLS event handler thing. So that only leaves me with reverting it for the time being.
Note that I had to bump the version of
@types/express-serve-static-core
due to the fact that it had the incorrect data type for the router (which is now public according to the changelog, instead of private as it used to be).This also highlights a significant issue regarding our process. We should have some systems in place that fail if the Electron build fails to run at all.