Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

bit Boilerplate compresses the library CSS and JS again instead of serving their published .br

Open
  • Is something wrong?
#14,068 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@yasmoradi is already working on this.

Since Oct 21, 2026.

  • #14069 by @yasmoradi — open

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp, css, wasm
Domain
backend, performance

Research direction

Start by reading how Server.Web serves library files under _content through UseStaticFiles, how UseResponseCompression handles those responses, and how UseBlazorFrameworkFiles serves published .br files under _framework. Compare the delivered CSS and JS sizes with their published Brotli files; done means the library assets use the published compressed files without being compressed again. Linked pull request #14069 is already open.

Written by the indexing model from the issue text.

Description

Without MapStaticAssets (#14059), bit Boilerplate's Server.Web serves the library files under _content through UseStaticFiles, which doesn't know about the .br files the publish writes next to them. UseResponseCompression then compresses each one again at its fastest level: on adminpanel.bitplatform.dev bit.blazorui.css reaches the browser as 165 KB of Brotli while its published .br is 71 KB, and bit BlazorUI's, Extras' and Butil's CSS and JS together cost about 175 KB more than their published files on a first visit.

_framework doesn't have this problem: UseBlazorFrameworkFiles serves its published .br files.

Dominant language
C#
Stars
1.4k
Forks
264
Avg merge
14h 17m
Merged PRs (30d)
327

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bitfoundation/bitplatform

All issues in bitfoundation/bitplatform

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.