Skip to content

Browserify a forked repository. #205

Description

@NikoEscobar

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions