WICG / WICG/webpackage

go/bundle explain how to use gzip with this

Open
#841 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
1.3k
Forks
125
PR merge metrics
No merged PRs in 30d

Description

Web bundles have header information, I know gzip packaging uses headers to help work, and web bundle is definitely not compressed by default as zip vs wbn comparisons I've done shows wbn is larger by a decent amount.

Part of the states goal of web bundles is to work in areas with little internet. Typically this comes hand in hand with low on device storage. Thus, I think gzipping the contents of a web bundle probably would make a user more willing to use and keep these files. I'm not familiar enough with the format to know how to do that, but it would be a good tutorial to publish to help app makers get the most out of the format.

From my comparison I zipped a pico8 game called lava joe and it was 557KB, whereas the wbn version was 1.81 MB. I also ran into an issue where the game didn't run to well in web bundle format because navigation to different url #fragment broke it in chrome, but I'll assume it would have worked without this

Contributor guide

Open the contributing guide

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.

Research direction

The issue names no repository file or test. Start by checking the web bundle format and existing documentation to determine whether gzip applies to bundle contents; done means publishing a clear tutorial that explains the supported workflow and its limitations.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.