mapbox / mapbox/duplicate-module-test
Fail or warn when module isn't found?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Right now if a module isn't found, we exit `1` and fail. Output looks like this:
```
Checking for duplicate modules ...
tilelive was not found in the node_modules tree
```
Alternatively, we could just print a warning since this isn't necessarily a bad thing, it just means the module isn't being installed (presumably because it's not longer being used). Output could instead look like:
```
Checking for duplicate modules ...
✔ @mapbox/vtquery has only one version
? tilelive was not found in the node_modules tree
```
cc @mapbox/core-tech
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
No file, test, or entry point is named. Start by locating the code that handles a module missing from the node_modules tree and review how its exit status and output are tested. Done means the project has a decided fail-or-warn behavior, matching output, and coverage for the missing-module case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100