Update sample js packages - #1032

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 53.12%. Comparing base (00fa787) to head (f74e2dd).
⚠️ Report is 1 commits behind head on develop.
✅ All tests successful. No failed tests found.

@@           Coverage Diff            @@
##           develop    #1032   +/-   ##
========================================
  Coverage    53.12%   53.12%           
========================================
  Files          258      258           
  Lines        19414    19414           
  Branches      1417     1417           
========================================
  Hits         10313    10313           
  Misses        8626     8626           
  Partials       475      475           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@s3cody not sure about pinning to typescript 6, what do we need to do to get upgraded to 7?

TypeScript 7 is the native Go port, and the stable compiler API used by this sample's webpack stack is not available yet. Both ts-loader and fork-ts-checker-webpack-plugin call the old API. That is what caused the original CI failures (readConfigFile is not a function / missing fileExists).

I reproduced this locally with 7.0.2. After changing module + moduleResolution to Node16 and removing ignoreDeprecations, npm run typecheck passes, but electron-forge package still fails in those two webpack integrations.

So the upgrade needs one of:

1. Wait for TS7-compatible releases of ts-loader and fork-ts-checker-webpack-plugin (my preference for a sample), or
2. Replace them with a transpile-only webpack loader such as SWC/esbuild, run tsc --noEmit as a separate pre-package check, and migrate the tsconfig options above.

For now, keeping TS 6 pinned while taking the Electron update is the small/safe option. The pin can come out once the webpack stack supports TS7.