Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[question] Why didn't downloads for the dependent @jsenv/node-module-import-map increase? #380

Open
t2ym opened this issue Aug 19, 2020 · 0 comments
Labels

Comments

@t2ym
Copy link
Owner

t2ym commented Aug 19, 2020

[question] Why didn't downloads for the dependent @jsenv/node-module-import-map increase?

Description

  • @jsenv/node-module-import-map was added as a dependency
  • a certain amount of increase in npm download stats for thin-hook
  • Download stats for @jsenv/node-module-import-map did not change
    • Significantly less than thin-hook

https://npm-stat.com/charts.html?package=thin-hook&package=%40jsenv%2Fnode-module-import-map&from=2019-08-18&to=2020-08-18

Suspected Situation

  • thin-hook download stats are not by NPM but mainly by 3rd party CDN servers which do not automatically download dependencies
  • @jsenv/node-module-import-map is popular and already cached at NPM clients
  • Due to Update npm package dependencies #374, the current (0.4.0-alpha.30 or earlier) thin-hook NPM package is awkward to handle without package-lock.json, which is missing in the NPM package
@t2ym t2ym added the question label Aug 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant