404 Not Found
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 41
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
```sh
% npm install @mapbox/vtcomposite --save
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@mapbox%2fvtcomposite - Not found
npm ERR! 404
npm ERR! 404 '@mapbox/vtcomposite@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/honjyo/.npm/_logs/2022-11-24T08_07_46_624Z-debug.log
```
Contributor guide
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
Reproduce the reported `npm install @mapbox/vtcomposite --save` command and inspect the package’s npm publication state. The issue names no source file or test; first determine whether the intended outcome is to publish the package or document a different installation method, then verify installation from the npm registry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100