-
Notifications
You must be signed in to change notification settings - Fork 10.4k
[release/3.1] Update SPA template JS dependencies #42060
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Hi @MackinnonBuck. If this is not a tell-mode PR, please make sure to follow the instructions laid out in the servicing process document. |
Should the corresponding |
The |
Let's wait to merge this - I still need to complete some validations. |
@MackinnonBuck let me know when you want this merged (branches are open until EOD Monday) |
Why is this a |
@dougbu Last month's dependency updates introduced a bug that is fixed by importing |
I defer to @Pilchie |
Let's split the difference - instead of just applying the label, let's actually send a mail to tactics with info about the change so that it's more broadly known, but not block on approval. |
@wtgodbe I've completed my validations and the mail has been sent to tactics - can this be approved/merged now? |
Since @javiercn is likely done for the day, I could approve but it would be better for someone at least slightly familiar w/ these two packages. Let me know if there's no one else around today |
Thanks @javiercn❕ |
Update SPA template JS dependencies
Includes the routine update for SPA template dependencies. In addition,
.js
files importingreact-router
now instead importreact-router-dom
to accommodate a breaking change in a previous JS package update.Description
This PR makes two changes:
react-router
andreact-router-dom
, which only manifested itself as a real problem in the 3.1.25 SPA templates. The fix is to change all.js
files importingreact-router
to instead importreact-router-dom
.Fixes https://github.com/aspnet/AspNetCore-ManualTests/issues/1380
Customer Impact
Without the code change, customers will have to manually make the change themselves for all new SPA projects created from the templates in .NET Core 3.1. Without this fix, the error message that gets logged does not make the required code change obvious to customers.
Regression?
Regressed from .NET Core 3.1.24
Risk
The fix simply adjusts our code to reference the correct package (
react-router-dom
instead ofreact-router
). Other changes are the routine JS dependency updates.Verification
Packaging changes reviewed?