browserify / browserify/wzrd.in
Browserify a forked repository.
- Dominant language
- JavaScript
- Stars
- 637
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I'm having a hard time trying to figure it out a way to browserify a forked repository
I'm not totally sure what happens under the hood of wzrd.in or if this is even possible to be accomplished,
Here is an example of my package.json dependecies, I assume that if I'm able to get a forked package this way, through npm, wzrd.in should be as well, is that right?
```
"dependencies": {
"three-bmfont-text": "dmarcos/three-bmfont-text#1babdf8507",
}
```
if I insert "dmarcos/three-bmfont-text#1babdf8507" on the version field
The response I receive is: **Cannot GET /standalone/[email protected]/three-bmfont-text**
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the package.json dependency using dmarcos/three-bmfont-text#1babdf8507 and reproduce the request against the wzrd.in standalone endpoint. Inspect how wzrd.in resolves git-based dependencies and determine whether the endpoint should support this form; done means a confirmed behavior and an agreed change or documented limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100