fix: drop nuget bootstrap and popper.js, npm bundles take over

Removing the 'bootstrap' and 'popper.js' NuGet package references
that were used solely to copy assets to wwwroot/ at build time.
The npm-based esbuild bundles now provide the same files, and the
duplicate-asset build error is gone.

'bootstrap 5.3.8' (NuGet) was flagged with vulnerabilities by
Dependabot. Pinning to 4.6.2 via npm (matching what the views
were using from wwwroot/lib/) is closer to what the rest of the
codebase expects.

Verified: 'dotnet test' passes (11/11).

Refs: this is the fix to make the 'separate front assets into
esbuild bundles' commit green.
This commit is contained in:
Paul Schneider 2026-06-14 14:24:55 +01:00
commit cef6002fef
2 changed files with 0 additions and 8 deletions

View file

@ -9,12 +9,6 @@
<RepositoryUrl>https://github.com/pazof/yavsc</RepositoryUrl>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="popper.js">
<PrivateAssets>all</PrivateAssets>
</PackageReference>
<PackageReference Include="bootstrap">
<PrivateAssets>all</PrivateAssets>
</PackageReference>
<PackageReference Include="HigginsSoft.IdentityServer8" />
<PackageReference Include="HigginsSoft.IdentityServer8.AspNetIdentity" />
<PackageReference Include="HigginsSoft.IdentityServer8.EntityFramework" />