Skip to content

Conversation

@pavelsavara
Copy link
Member

force update of the src\Components\Web.JS\@types\dotnet npm package

in order to fix stale files in src\Components\Web.JS\node_modules\@types\dotnet as reported in #45993

note that just bumping the version in src\Components\Web.JS\@types\dotnet\package.json would not help as it's only refered to by src\Components\Web.JS\package.json as path to directory, not a versioned module.

@pavelsavara pavelsavara self-assigned this Jan 10, 2023
@pavelsavara pavelsavara added the feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly label Jan 10, 2023
@pavelsavara pavelsavara added this to the 8.0 milestone Jan 10, 2023
Copy link
Contributor

@TanayParikh TanayParikh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @pavelsavara!

@DamianEdwards could you please try this out if you're still running into that issue?

@pavelsavara pavelsavara marked this pull request as ready for review January 10, 2023 18:25
@pavelsavara pavelsavara requested review from a team, dougbu and wtgodbe as code owners January 10, 2023 18:25
@DamianEdwards
Copy link
Member

@TanayParikh Not sure about this specific change, but I've verified that running clean.cmd before the build resolves the issue I saw.

@TanayParikh TanayParikh merged commit 3416f8a into dotnet:main Jan 10, 2023
@ghost ghost modified the milestones: 8.0, 8.0-preview1 Jan 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants