Not able to use standalone & require flags at the same time
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- build-system
Research direction
Start by reviewing browser-pack/index.js lines 44-52 and the linked browserify issue to understand why standalone and require flags are currently treated as incompatible. Investigate the surrounding bundling behavior and define done as producing a bundle that works both standalone and as a required dependency without breaking either use case.
Written by the indexing model from the issue text.
Description
As notified at https://github.com/substack/node-browserify/issues/939, I'm not able to generate a bundle that at the same time can be used standalone and also export its content so it can be required by other bundles, that it's useful for frameworks that can use build-in and external plugins at the same time. Reviewing the code, there's a conditional that explicit forbit this use case, so I would like to know if it's on purposse and why, or if this could be fixed for this use case (I think it's possible, but needs to investigate a little bit more the code...).
- Dominant language
- JavaScript
- Stars
- 170
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from browserify/browser-pack
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
browserify/browser-pack#93 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
browserify/browser-pack#90 ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
browserify/browser-pack#88 · 2 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
browserify/browser-pack#42 · 2 reactions ·
All issues in browserify/browser-pack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
neondatabase/website#6038 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Effect-TS/effect#8728 · 1 comment ·
Maintainers usually reply within 1 day
-
[quality] coverage gate exits 0 when the test run is killed by a signal (tests/tools/coverage-report.mjs:680 `?? 1` is untested)Possibly taken @hivecommons-hive claimed this today. Openagent/quality hive/covered-by-pr hive/hosted-available-lke648397-260827-5n31 quality testing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day