incompatibility with "npm run" and extra arguments

If I have a script like "compile": "tsup ./app/cli.ts ./app/index.ts --metafile" and want to pass in more args I can’t via the npm run command.

When passing in more args via npm run compile -- --external=@vmngr/libvir they’re ignored since they’re passed in quoted.

❯ npm run compile -- --external=@vmngr/libvir

> @unraid/api@2.41.1 compile C:\Users\xo\code\unraid\api
> tsup ./app/cli.ts ./app/index.ts --metafile "--external=@vmngr/libvir"

[HyperCrowd]

To add to the pain, if this was in an npm script for dev:

tsup-node --onSuccess 'node -r source-map-support/register dist/index.js'

It obviously would have no way to pass dynamic CLI commands for commanderjs or yargs via npm run dev -- someArg

It works if you hard code the args:

tsup-node --onSuccess 'node -r source-map-support/register dist/index.js someArg'

But that makes CLI testing a minor inconvenience

[OmgImAlexis]

❯ npm run compile -- --external @vmngr/libvir

> @unraid/api@2.42.1 compile C:\Users\xo\code\unraid\api
> tsup --metafile "--external" "@vmngr/libvir"

CLI Building entry: {"cli":"app/cli.ts","index":"app/index.ts"}
CLI Using tsconfig: tsconfig.json
CLI tsup v5.12.1
CLI Using tsup config: C:\Users\xo\code\unraid\api\package.json
CLI Target: node12
CJS Build start
✘ [ERROR] Could not resolve "@vmngr/libvirt"

    app/core/utils/vms/get-hypervisor.ts:8:55:
      8 │ import { ConnectListAllDomainsFlags, Hypervisor } from '@vmngr/libvirt';
        ╵                                                        ~~~~~~~~~~~~~~~~

  You can mark the path "@vmngr/libvirt" as external to exclude it from the bundle, which will
  remove this error.