v1.0.2

jpm 1.0.2: jpx without Node.js.

curl -fsSL https://getjpm.sh | sh                  # macOS and Linux

irm https://getjpm.sh/install.ps1 | iex              # Windows

jpx without Node

• A native tool runs as itself. @sentry/cli, esbuild, turbo and others ship their bin as a
  small Node script that starts the real program from a package per platform. With no Node on
  the PATH, jpx @sentry/cli now runs that program directly instead of failing with
  env: 'node': No such file or directory. With Node, the package's own launcher runs as before.
• --node and --bun. jpx --node <pkg> installs the current Node.js LTS with the command,
  first on its PATH; jpx --bun <pkg> installs the latest Bun and runs the bin's
  #!/usr/bin/env node under it, as bun --bun does.
• -p node@runtime:<range> (bun@, deno@) installs that runtime with the command, checked
  as jpm checks runtimes it installs as dependencies.
• A JavaScript CLI with no Node to run it now says so: <pkg>'s <bin> runs on Node, which is not on PATH: add --node or --bun to install one.

Full changes: v1.0.1...v1.0.2