Blazor.BrowserExtension

Fixed paths in scoped CSS not replaced (Issue https://github.com/mingyaulee/Blazor.BrowserExtension/issues/77)

Full Changelog: https://github.com/mingyaulee/Blazor.BrowserExtension/compare/v0.12.1...v0.12.2

• Allow comments in manifest.json

Full Changelog: https://github.com/mingyaulee/Blazor.BrowserExtension/compare/v0.12.0...v0.12.1

Breaking changes:

• .Net 5.0 support is now dropped
• Initial support for .Net 8.0

Full Changelog: https://github.com/mingyaulee/Blazor.BrowserExtension/compare/v0.11.0...v0.12.0

Breaking changes::

• Custom initialization parameter is changed from environmentName: string to blazorStartOptions: object. Refer to the updated readme.

Release is marked as deprecated as the package has broken runtime.

• Reverted exclusion of brotli compression for dotnet.wasm
• Use System.Text.Json for parsing manifest during validation

• Updated dotnet.js runtime to 7.0.3
• Updated project dependencies
• Fixed brotli decode error for dotnet.wasm
• Updated template to match default Blazor app template

Updated blazor.boot.json replacement tokens as optional

Disabled Blazor caching by default to prevent taking up storage when loaded in content scripts.

Fixed paths in blazor.boot.json not replaced (Issue #46)

Fixed publish process miss out removing some compressed files

• Added support for browser extension manifest V3.
• Updated browser polyfill to v0.10.0

Added .Net 7 as target framework

Fixed error when processing JSON static web assets manifest which has existing content or framework node (Issue #36)

• Easier debugging without the need to change any part of the code
• Updated WebExtensions.Net to v0.10.1

• Added .Net 6 as target framework.
• Updated JsBind.Net and WebExtensions.Net package reference version.

• Updated JsBind.Net and WebExtensions.Net package reference version.
• Fixed compatibility with .Net 6 runtime JavaScript file.
• Updated template package reference version for .Net 6 target framework.

• Use config file instead of replacing tokens in JavaScript files
• Script assets are now included as static web assets/RCL assets instead of linked files
• Fix error when resolving XML static web asset path that contains relative path (i.e. basepath/../filepath)
• Update JsBind.Net from v0.1.4 to v0.2.5 and WebExtensions.Net from v0.9.0 to v0.9.2

Breaking changes:

• MsBuild property LinkBrowserExtensionAssetsPath is removed
• Projects with content script need to use app.js pre-initialization script
• Option is removed from the service dependency registration
• Path to ContentScript.js and Core.js is changed from "BrowserExtensionScripts" to "content/Blazor.BrowserExtension"
• Global variable in JavaScript to change initialization behaviour is now within the "BlazorBrowserExtension" object

Migration Guide:

1. Update Program.cs to remove the configuration action in the .AddBrowserExtensionServices() parameter

   // Before
   builder.Services.AddBrowserExtensionServices(options =>
   {
       options.ProjectNamespace = typeof(Program).Namespace;
   });
   // After
   builder.Services.AddBrowserExtensionServices();
   

2. Update index.html and manifest.json and anywhere with reference to the scripts from this package from "BrowserExtensionScripts/" to "content/Blazor.BrowserExtension/"

   <!-- Before -->
   <script src="BrowserExtensionScripts/Core.js"></script>
   <!-- After -->
   <script src="content/Blazor.BrowserExtension/Core.js"></script>
   

3. "BrowserExtensionScripts/*" can be removed from the web_accessible_resources key in manifest.json

Projects with content scripts

1. Add a new file named app.js under the directory wwwroot
2. Add the following code into the new file.

   if (globalThis.BlazorBrowserExtension.BrowserExtension.Mode === globalThis.BlazorBrowserExtension.Modes.ContentScript) {
     const appDiv = document.createElement("div");
     appDiv.id = "My_Unique_Extension_App_Id"; // this ID should be the same as the container ID in the index.html file
     document.body.appendChild(appDiv);
   }
   

3. Add "app.js" to the web_accessible_resources key in manifest.json

Projects with custom initialization behaviour
Move the initialization logic into app.js file. Refer to the readme to read on the way to change initialization behaviour in this version.

Fix JsHttpClient request headers in fetch options

Fix JSON StaticWebAssets manifest parser relative directory to preserve folder structure

• Read StaticWebAssets manifest in JSON format (introduced in .Net 6 RC1)
• Handle manifest resource type when loading boot resources (to support .Net 6 RC1)
• Fix JsHttpClient script not included in package