[rush-serve-plugin] [lockfile-explorer] Upgrade express to 5.1.0#5350
[rush-serve-plugin] [lockfile-explorer] Upgrade express to 5.1.0#5350cmalonzo wants to merge 3 commits intomicrosoft:mainfrom
Conversation
|
Do we know if this impacts compatibility with http2-express-bridge? Last publish of that package was 4 years ago. |
|
@dmichon-msft The @types/express version didnt need to change with the express bump and it looks like http2-express-bridge only depends on the former. Are there specific debug steps I can take to test this? |
|
Temporarily: {
"$schema": "https://developer.microsoft.com/json-schemas/rush/v5/rush-serve-plugin-options.schema.json",
"phasedCommands": ["start"],
"portParameterLongName": "--port",
"globalRouting": [
{
"workspaceRelativeFolder": "rush.json",
"servePath": "/"
}
],
"buildStatusWebSocketPath": "/ws",
"logServePath": "/logs"
}Also add the following entry in the {
"longName": "--port",
"argumentName": "PORT_NAME",
"parameterKind": "integer",
"description": "If specified, Rush will serve files on the specified port.",
"associatedPhases": [],
"associatedCommands": ["start"]
},Then run |
|
It appears that this value needs to be updated: |
|
Abandoning for an alternative change |
Summary
Bump
expressversion to5.1.0, addressing npm audit report vulnerabilities as described in #5327Details
Details in bug #5327
How it was tested
Testing lockfile-explorer
Testing rush-serve-plugins
In progress
Impacted documentation