-
Notifications
You must be signed in to change notification settings - Fork 10.3k
[Blazor] Update npm dependencies #36088
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
cf5c289
to
a215d17
Compare
src/Components/WebAssembly/Authentication.Msal/src/Interop/webpack.config.js
Outdated
Show resolved
Hide resolved
src/Components/WebAssembly/Authentication.Msal/src/Interop/webpack.config.js
Outdated
Show resolved
Hide resolved
src/Components/WebAssembly/WebAssembly.Authentication/src/Interop/webpack.config.js
Outdated
Show resolved
Hide resolved
src/Components/WebAssembly/WebAssembly.Authentication/src/Interop/webpack.config.js
Outdated
Show resolved
Hide resolved
src/Components/WebAssembly/WebAssembly.Authentication/src/Interop/webpack.config.js
Outdated
Show resolved
Hide resolved
...ssembly.Authentication/src/Microsoft.AspNetCore.Components.WebAssembly.Authentication.csproj
Show resolved
Hide resolved
.../WebAssembly/testassets/Wasm.Authentication.Server/Data/Migrations/20210902111722_Initial.cs
Show resolved
Hide resolved
.../WebAssembly/testassets/Wasm.Authentication.Server/Data/Migrations/20210902111722_Initial.cs
Show resolved
Hide resolved
src/ProjectTemplates/BlazorTemplates.Tests/BlazorWasmTemplateTest.cs
Outdated
Show resolved
Hide resolved
It is not worth having this test since it creates issues as it tries to hit Azure AD when run.
Co-authored-by: Steve Sanderson <[email protected]>
…pack.config.js Co-authored-by: Steve Sanderson <[email protected]>
…pack.config.js Co-authored-by: Steve Sanderson <[email protected]>
c9d4def
to
93a3b43
Compare
🆙📅 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updates look great!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just some minor items
src/Components/WebAssembly/Authentication.Msal/src/Interop/dist/.gitignore
Show resolved
Hide resolved
src/Components/WebAssembly/WebAssembly.Authentication/src/Interop/dist/.gitignore
Show resolved
Hide resolved
...mponents/WebAssembly/testassets/Wasm.Authentication.Server/Wasm.Authentication.Server.csproj
Show resolved
Hide resolved
Just tried out this branch locally, and it's seems to have fixed a lot of the random issues I was seeing with the |
/backport to release/6.0-rc1 |
Started backporting to release/6.0-rc1: https://github.com/dotnet/aspnetcore/actions/runs/1212823832 |
@javiercn backporting to release/6.0-rc1 failed, the patch most likely resulted in conflicts: $ git am --3way --ignore-whitespace --keep-non-patch changes.patch
Applying: Update packages
Applying: Update codebase for new typescript errors
Applying: Update dependencies
Applying: update WebAssembly.Authentication npm packages
Applying: Update webassembly
Applying: Integrate with the build
Applying: Update build process for MSAL
Applying: Update msal-browser version
Applying: Partially fix errors
Applying: Update and fix test project
Applying: Update npm dependencies
Applying: Remove unnecessary dependency
Applying: Update JS files
warning: Cannot merge binary files: src/Components/Web.JS/dist/Release/blazor.webview.js (HEAD vs. Update JS files)
warning: Cannot merge binary files: src/Components/Web.JS/dist/Release/blazor.server.js (HEAD vs. Update JS files)
Using index info to reconstruct a base tree...
M src/Components/Web.JS/dist/Release/blazor.server.js
M src/Components/Web.JS/dist/Release/blazor.webview.js
Falling back to patching base and 3-way merge...
Auto-merging src/Components/Web.JS/dist/Release/blazor.webview.js
CONFLICT (content): Merge conflict in src/Components/Web.JS/dist/Release/blazor.webview.js
Auto-merging src/Components/Web.JS/dist/Release/blazor.server.js
CONFLICT (content): Merge conflict in src/Components/Web.JS/dist/Release/blazor.server.js
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0013 Update JS files
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128 Please backport manually! |
/backport to release/6.0 |
Started backporting to release/6.0: https://github.com/dotnet/aspnetcore/actions/runs/1212836726 |
@javiercn backporting to release/6.0 failed, the patch most likely resulted in conflicts: $ git am --3way --ignore-whitespace --keep-non-patch changes.patch
Applying: Update packages
Applying: Update codebase for new typescript errors
Applying: Update dependencies
Applying: update WebAssembly.Authentication npm packages
Applying: Update webassembly
Applying: Integrate with the build
Applying: Update build process for MSAL
Applying: Update msal-browser version
Applying: Partially fix errors
Applying: Update and fix test project
Applying: Update npm dependencies
Applying: Remove unnecessary dependency
Applying: Update JS files
warning: Cannot merge binary files: src/Components/Web.JS/dist/Release/blazor.webview.js (HEAD vs. Update JS files)
warning: Cannot merge binary files: src/Components/Web.JS/dist/Release/blazor.server.js (HEAD vs. Update JS files)
Using index info to reconstruct a base tree...
M src/Components/Web.JS/dist/Release/blazor.server.js
M src/Components/Web.JS/dist/Release/blazor.webview.js
Falling back to patching base and 3-way merge...
Auto-merging src/Components/Web.JS/dist/Release/blazor.webview.js
CONFLICT (content): Merge conflict in src/Components/Web.JS/dist/Release/blazor.webview.js
Auto-merging src/Components/Web.JS/dist/Release/blazor.server.js
CONFLICT (content): Merge conflict in src/Components/Web.JS/dist/Release/blazor.server.js
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0013 Update JS files
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128 Please backport manually! |
* Updates npm dependencies to their latest versions. * Standardizes build process for our JS dependencies on webpack 5 with babel, etc. * Updates dependencies for the auth packages to their latest versions. * Fixes test assets so that they can be run locally.
* Updates npm dependencies to their latest versions. * Standardizes build process for our JS dependencies on webpack 5 with babel, etc. * Updates dependencies for the auth packages to their latest versions. * Fixes test assets so that they can be run locally.
Updates our NPM dependencies and upgrades the auth projects to use webpack5 inline with the rest of the Blazor projects