ABP 10.0.1 : global.js bundle has incorrect dotnet.js path for Blazor WebAssembly (Standalone)

[omer-repo]

Is there an existing issue for this?

• I have searched the existing issues

Description

After upgrading from ABP 9.3.3 to ABP 10.0.0 (.NET 10), the Blazor WebAssembly project fails to start because dotnet.js cannot be found. The global.js file generated by abp bundle command contains an incorrect relative path.
Error message:
Failed to start platform. Reason: TypeError: Failed to fetch dynamically imported module: https://localhost:44307/dotnet.js

Problem Details
The global.js file generated by the abp bundle command has a different path for loading dotnet.js.

global.js in ABP 9.3.3 / .NET 9 (Working):

let t = "_framework/dotnet.js";
// ...
const n = new URL(t, document.baseURI).toString();
return await import(n)

global.js in ABP 10.0.1 / .NET 10 (Broken):
return await import("./dotnet.js")

Root Cause
The global.js bundle includes content from blazor.webassembly.js. In .NET 10, the blazor.webassembly.js changed to use a relative path ("./dotnet.js") instead of the explicit "_framework/dotnet.js" path.
This works when blazor.webassembly.js is located inside _framework folder, but ABP's bundle mechanism places global.js in the root wwwroot directory, not in _framework.

Reproduction Steps

1. Take an existing Blazor WebAssembly (Standalone) project created with ABP 5, 6, 7 (the original standalone WASM project structure with index.html)
2. Upgrade to ABP 10.0.1 + .NET 10 (From ABP 9.x)
3. Run abp bundle command
4. Start the project (dotnet run)
5. Open browser console - you will see the dotnet.js not found error

Expected behavior

The abp bundle command should generate global.js with the correct path for dotnet.js. Since global.js is placed in the root wwwroot directory, it should use "_framework/dotnet.js" or calculate the absolute path using new URL() as it was done in previous versions.

Actual behavior

No response

Regression?

No response

Known Workarounds

Workaround 1: Manually fix the path in global.js
Manually modify global.js after running abp bundle:

Find:
return await import("./dotnet.js")

Replace with:
return await import("_framework/dotnet.js")

Result: This partially works - the DLL/WASM files are loaded and the initial page appears, but then the application crashes with multiple errors:
dotnet.js:4 Uncaught (in promise) Error: Assert failed: .NET runtime already exited with 1

Error: Assert failed: .NET runtime already exited with 1 [object Object]. 
You can use runtime.runMain() which doesn't exit the runtime.
    at Be (dotnet.js:4:22402)
    at Object.He [as assert_runtime_running] (dotnet.js:4:22546)
    at Object.<anonymous> (invoke-cs.ts:140:23)
    at Object.endInvokeJSFromDotNet (global.js:1:46844)
    at w.beginInvokeJSFromDotNet (global.js:1:4330)

Workaround 2: Copy dotnet.js to root
Copying dotnet.js to the root directory causes the same issue - the file then tries to load other runtime files from the wrong location.

Note: All workarounds are lost every time abp bundle is executed.

Version

10.0.1

User Interface

Blazor

Database Provider

EF Core (Default)

Tiered or separate authentication server

None (Default)

Operation System

Windows (Default)

Other information

ABP Framework Version: 10.0.1
.NET Version: 10.0
Project Type: Blazor WebAssembly (Standalone) - NOT the Blazor Web App introduced in .NET 8
Operating System: Windows 11
Previous Working Version: ABP 9.3.3
Project History: This is a long-running project that has been upgraded through ABP versions starting from ABP 6. It uses the original Blazor WebAssembly (Standalone) project structure, not the newer Blazor Web App (Server + Client) structure introduced in .NET 8.

[maliming]

hi

The abp bundle command is outdated.

Can you try to use the latest global assets feature? You can create a new template project to check the new code.

https://github.com/abpframework/abp/blob/dev/docs/en/Community-Articles/2024-11-25-Global-Assets/POST.md
https://abp.io/docs/latest/framework/ui/blazor/global-scripts-styles

Thanks.

[omer-repo]

Thank you for your response.

I checked both pages and the responses in the https://abp.io/support/questions/10166/Global-Assetsglobaljs also. I need clarification regarding my project structure:

My Current Setup

• Project Type: Blazor WebAssembly Standalone (not Blazor Web App)
• SDK: Microsoft.NET.Sdk.BlazorWebAssembly
• Entry Point: index.html (not App.razor)
• No Host/Server Project - The application runs entirely in the browser

This is a long-running project that has been upgraded through multiple ABP versions (from ABP 6.x to ABP 10.x). It uses the original Blazor WebAssembly Standalone structure with wwwroot/index.html, not the newer Blazor Web App (Server + Client) structure introduced in .NET 8.

My Questions

1. Is the new Global Assets feature compatible with Standalone WebAssembly projects?

   Based on the AI Bot's response and documentation, it seems global.js is now dynamically generated by a host server project using app.MapAbpStaticAssets(). Since Standalone WASM has no server-side host, this mechanism cannot work.

2. Do I need to migrate to the Blazor Web App structure?

   If Global Assets requires a host project, does this mean all existing Standalone WASM projects must be migrated to the new Blazor Web App (Server + Client) architecture to work with ABP 10.x?

3. Is there a workaround for Standalone WASM?

   Is there any alternative approach for Standalone WASM projects, such as:

   • A build-time bundle generation (similar to the old abp bundle command)?
   • Manually including the required scripts from _content/Volo.Abp.../ paths?
   • I tried to copy a global.js content from a fresh solution with ABP 10.0.1 and added blazor.webassembly.js reference to index.html. But it gave hundreds error in the console

<!--ABP:Scripts-->
<script src="global.js?_v=639025618497898509"></script>
<!--/ABP:Scripts-->
<script src="_framework/blazor.webassembly.js"></script>

What I'm Looking For

Please advise whether:

1. Standalone WASM is still supported in ABP 10.x, and if so, how to configure bundling without a host project.

2. Migration is required - If Standalone WASM is no longer supported, please provide a migration guide from Standalone WASM to Blazor Web App structure.

Thank you for your help!

[maliming]

hi

1. No
2. I recommend that you do this, ASP.NET Core also recommends this.
3. You can create a new Blazor project with the latest ABP Studio, then check the new solution structure and module code.

Please check this document and ignore the ABP Bundle section.

https://abp.io/docs/latest/release-info/migration-guides/abp-8-2-blazor-web-app#the-key-changes-of-the-new-blazor-web-app-template

New ABP Bundle:
https://github.com/abpframework/abp/blob/dev/docs/en/Community-Articles/2024-11-25-Global-Assets/POST.md
https://abp.io/docs/latest/framework/ui/blazor/global-scripts-styles

[omer-repo]

Thanks for the clarification.

I checked the migration guide you shared:
https://abp.io/docs/latest/release-info/migration-guides/abp-8-2-blazor-web-app#the-key-changes-of-the-new-blazor-web-app-template

However, I’m confused because the document seems inconsistent with current ABP 10 templates and with the recommendations given in this issue.

1) The guide is very high-level / missing a concrete migration path (Standalone WASM -> new -u blazor template)

We have an existing long-running Standalone Blazor WebAssembly app (single project, Microsoft.NET.Sdk.BlazorWebAssembly, wwwroot/index.html).

The guide describes the new template concepts, but it does not provide a step-by-step migration path specifically for:

• Standalone WASM -> the new “hosted WASM” style template generated via -u blazor (host project + .Client project)

This is also mentioned in ABP support question #8412 where “Option A” and “Option B” are discussed:
https://abp.io/support/questions/8412/Migrate-from-832-Blazor-Webassembly-to-Blazor-Web-App

I prefer Option A (host project + .Client WASM, render mode InteractiveWebAssembly(prerender:false)).

2) The migration guide still contains an “ABP Bundle” section, but abp bundle is said to be obsolete

In this issue, the answer says the abp bundle command is outdated and we should use the new Global Assets feature.

But the migration guide still contains an “ABP Bundle” section that:

• explicitly instructs running abp bundle
• and mentions settings like IsBlazorWebApp / InteractiveAuto

In ABP 10 generated solutions (via ABP CLI / ABP Studio), I can’t find these keys in appsettings.json anymore.

Could you confirm:

• Is the “ABP Bundle” section in that migration guide outdated and should be removed/updated?
• Is “Global Assets” the replacement approach for that section?

3) About ABP CLI template selection: is -u blazor the correct target for migrating Standalone WASM?

To migrate, I generated a new solution using:
abp new <Name> -t app -u blazor

This produces a host project + a .Client project (WASM), with App.razor in the host project using InteractiveWebAssembly(prerender:false).

Is this the correct template to migrate an old Standalone WASM app to in ABP 10?
If yes, are there any known migration pitfalls or required steps not covered by the docs (especially around global scripts/styles and authentication - I'm using custom AuthenticationStateProvider in Blazor)?

Thank you.

[maliming]

hi

The new Blazor project will include a host and a client project. Your components will be added to the Client project.

The host is responsible for booting the Blazor app and providing the global.js and global.css.

You can run the template project to see how it works.

Thanks.