Support dynamic standalone module name, based on source file name
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- build-system
Research direction
Start by tracing how opts.standalone is handled while the source file path enters the browser-pack pipeline. Verify how the source filename is available at that point and compare the current true-value behavior with the requested /lib/alert.js to alert mapping. Done means opts.standalone === true derives the standalone name from the source file while preserving explicitly supplied names.
Written by the indexing model from the issue text.
Description
When running with opts.standalone, I would like the standalone name to be dynamic, based on the source file being packed.
For example, if the source file is /lib/alert.js, the standalone name should be set to alert.
I propose this be the default behavior if opts.standalone === true.
- 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 4/5 3-5 days Newbie friendliness 35/100
browserify/browser-pack#45 · 11 comments ·
All issues in browserify/browser-pack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
daisy/a11y-meta-viewer#18 ·
-
good first issue status: needs triaging type: bug version: 2.0
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
medusajs/medusa#17094 · 2 comments ·
Maintainers usually reply within 1 day
-
browser: chrome package: @carbon/react package: styles
Difficulty 1/5 Under an hour Newbie friendliness 92/100
carbon-design-system/carbon#23567 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
clerk/javascript#10033 ·
Maintainers usually reply within 1 day
-
bug client p1
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vercel/eve#4173 · 2 comments ·
Maintainers usually reply within 1 day