test: add test profiling script

[Bertie690]

What are the changes the user will see?

N/A

Why am I making these changes?

Makes it much easier to debug memory and performance bottlenecks in code.

What are the changes from a developer perspective?

Added a new script, pnpm test:profile, that instruments a Vitest test run, processes the generated profiler logs, and writes the results to disk to be viewed in a flamegraph tool.
I took the liberty of adding commander.js and its type-checked cousin as a dev dependency (which we really should be using, given how much it streamlines the whole process.argv pipeline)

Note

Given VS Code natively supports opening .cpuprofile and .memprofile files as a flamegraph, I saw it unnecessary to use an external tool to visualize them. (Also because I couldn't get it to work correctly.)

Screenshots/Videos

How to test the changes?

Run pnpm test:profile, then open the results in your flamegraph tool of choice. (VSCode has an extension for this, for what it's worth.)

Checklist

• The PR content is correctly formatted:
  • I'm using beta as my base branch
  • The current branch is not named beta, main or the name of another long-lived feature branch
  • I have provided a clear explanation of the changes within the PR description
  • The PR title matches the Conventional Commits format (as described in CONTRIBUTING.md)
• The PR is self-contained and cannot be split into smaller PRs
• There is no overlap with another open PR
• The PR has been confirmed to work correctly:
  • I have tested the changes manually
  • The full automated test suite still passes (use pnpm test:silent to test locally)
  • I have created new automated tests (pnpm test:create) or updated existing tests related to the PR's changes if necessary

[SirzBenjie]

It's worth noting that this is of limited usefulness due to our mocks. Most of our memory / performance bottlenecks are going to be due to the canvas and UI processing. That is effectively disabled here. We can optimize the 10%, but the other 90% is probably UI. Regardless, LGTM.

[Bertie690]

@SirzBenjie I'm more interested in why we got a sudden 50% spike in test duration.
This would help triage any unexpected increases in test time like prior

[DayKev]

So this doesn't allow passing arguments to Vitest, and it doesn't itself pass --silent="passed-only" to Vitest.

Also, I'm getting No CPU or memory profile found! when running it.

[Bertie690]

Please elaborate.

You need to make the vitest args the last ones passed to the function.

[DayKev]

Please elaborate.

You need to make the vitest args the last ones passed to the function.

PS I:\pokerogue repos\PokeRogue dev> pnpm test:profile tackle --silent

> pokemon-rogue-battle@1.11.13 test:profile I:\pokerogue repos\PokeRogue dev
> node scripts/profiling/profiling.js "tackle" "--silent"

📈 Test Profiler - v1.0.0

error: unknown option '--silent'

Usage: pnpm test:profile [options] <vitest-args...>

Run Vitest with Node's V8 profiler and generate processed profiling output.

Arguments:
  vitest-args          Arguments to pass directly to Vitest.

Options:
  -v, --version        Show the version number.
  -o, --output <path>  Directory to which V8 profiler output will be written. (Default: "./temp/vitest-profile")
  -c, --cpu            Enable CPU profiling. (Default: true)
  --no-cpu             Disable CPU profiling.
  -m, --memory         Enable memory profiling. (Default: true)
  --no-memory          Disable memory profiling.
  --clean              Whether to clean the output directory before writing new profiles.
  -h, --help           Show this help message.
 ELIFECYCLE  Command failed with exit code 1.