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

Browser Unpack Example Does Not Work

Open
#76 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
build-system

Research direction

Reproduce the shell commands with browserify@11.0.1, factor-bundle@2.5.0, and browser-unpack@1.1.1. Trace how factor-bundle handles the browser-unpack output, then verify that bundle/x.js and bundle/y.js are created with modules shared in bundle/common.js omitted.

Written by the indexing model from the issue text.

Description

$ browserify x.js y.js > bundle.js
$ browser-unpack < bundle.js | factor-bundle \
  x.js -o bundle/x.js \
  y.js -o bundle/y.js \
  > bundle/common.js

bundle/common.js is created. Neither bundle/x.js or bundle/y.js are created. It is my understanding that these bundles should be created with the modules that exist in the common bundle being omitted.

  • browserify@11.0.1
  • factor-bundle@2.5.0
  • browser-unpack@1.1.1
Dominant language
JavaScript
Stars
397
Forks
24
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 browserify/factor-bundle

All issues in browserify/factor-bundle

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.