My package-lock.json has a weird entry for :
"commander": {
"version": "2.15.1",
"resolved": "github:mateodelnorte/commander.js#9060bf880b791cf39245d425f1e8a41a55616781"
},
All other packages show up as resolved in our Virtual Repository defined in Artifactory
npm list commander@2.15.1 tells me ...
├─┬ d3@4.13.0
│ ├─┬ d3-dsv@1.0.8
│ │ └── commander@2.15.1 (github:mateodelnorte/commander.js#9060bf880b791cf39245d425f1e8a41a55616781)
│ └─┬ d3-request@1.0.6
│ └─┬ d3-dsv@1.2.0
│ └── commander@2.15.1 deduped (github:mateodelnorte/commander.js#9060bf880b791cf39245d425f1e8a41a55616781)
└─┬ react-scripts@3.4.4
└─┬ eslint-plugin-jsx-a11y@6.2.3
└─┬ aria-query@3.0.0
└── commander@2.15.1 deduped (github:mateodelnorte/commander.js#9060bf880b791cf39245d425f1e8a41a55616781)
What is special about this package? Is there anyway to avoid it resolving to github:mateodelnorte/commander.js
I know we can updates the direct dependencies that pull it in (which could be painful) but just trying to understand why it has the weird resolved value.
I did read at : https://github.com/mateodelnorte/meta/issues/26
Im having issues adopting this behind a proxy because of the github connection for commander module.
https://github.com/mateodelnorte/meta/blob/master/package.json#L36
Is there any way we can make this a NPM dependency?
and I think they did commander not to act weird, so I dont get the issues for later version e.g. this does not mention github:mateodelnorte/commander.js
├─┬ enzyme@3.11.0
│ └─┬ rst-selector-parser@2.2.3
│ └─┬ nearley@2.20.1
│ └── commander@2.20.3