You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
A server that only processes images with Bmage has to take Blazor and the editor along #14334
Up to 11.0.0-pre-10, Bmage had a Bit.Bmage.Core package: the engine, the managed codecs and the headless pipeline, with no dependencies at all (Bit.Bmage.Core.dll is 391 KB for net10.0). The restructure in #13966 folded it and Bit.Bmage.Editor into Bit.Bmage, so an ASP.NET Core API, a console tool or a worker that only resizes images now takes along:
Microsoft.AspNetCore.Components.Web, which a console app or a worker doesn't otherwise have.
The editor and the browser integration: Bit.Bmage.dll is 1.2 MB for net10.0.
Three static web assets, bit-bmage.js, bit-bmage-worker.js and bit-bmage-editor.css, published with the API under _content/Bit.Bmage.
Bmage's README calls it headless first and lists ASP.NET Core, console and worker hosts, and none of them use Blazor. bit Boilerplate's server API would be the first to hit this once Bmage can replace Magick.NET there (#14333).
Activity