javascriptdebug-js/debug #32Not a task: already works

No Git repository published in npm

envgap__debug-js__debug-32

Original GitHub issue ↗Dated source checkout ↗Opened 2012-12-19

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.

Not a benchmark task.

The project already builds and runs before the fix, so there is nothing to repair.

02 / ENVIRONMENT RECIPE

Base commit: cd0aec9e9163e4e9fe922b2f51b63ad3f62b4bc8
Manifest: package.json
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

debug-js/debug #32 · read the original issue

While you're publishing packages to npm, can you please push a repository URL too? Most package publishers provide a canonical Git URL where updates may be retrieved, which helps people and software tools discover the Git repository. If you're using the package.json file in the repository, you could add:

```
"repository" :
  { "type" : "git"
  , "url" : "git://github.com/visionmedia/debug.git"
  }
```

Then pushing these changes to npm would be awesome.

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]