mathisonian / mathisonian/requirify
Needs support on chrome:// URLs.
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 95
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
//cc @mathisonian I'm interested to paw along to fix this.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
The issue names no source files, tests, or entry points. Begin by reproducing the reported failure with a chrome:// URL in the browser console, then trace requirify's relevant loading path. Done means require() can load npm modules from chrome:// pages, with regression coverage if a suitable test location is found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100