Alternative: have the tool, when locally installed, try and update the databases all by itself. That way a new version doesn’t need to be released.

I quickly knocked something up in #11 to tackle this.

Open questions regarding the implementation:

• After having updated (with a locally changed package.json as a result), will a successive npm i -g @bramus/caniuse-cli work?
• Will that actually work on Windows (I have only tested on macOS)?
• What about yarn?
• Maybe there are better ways to do this?
  • Requiring npm and invoking things like npm.commands.view doesn’t seem like a viable option, as it’d only work with NPM.

Open questions regarding when to trigger this:

• Definitely not upfront.
• Maybe automatically after caniuse was invoked?
  • But only once per week, perhaps
• On a schedule?
• Also: give users an option to opt-out?

/cc @tunetheweb

Some more things I found:

• https://github.com/react-static/react-static/blob/85c232bb3d357e15b7efd04291ad43b4af2e976b/packages/react-static/src/commands/create.js#L219 invokes an execSync('yarnpkg --version', { stdio: 'ignore' }) to detect if yarn is present or not.
• https://github.com/npm/pacote is a project that fetches directly from NPMJS and unpacks the .tgz instead of going through the npm install … route.
• Lost the link, but some project allowed passing in your preferred package manager (npm, yarn, pnpm, bun) using a flag.