Unknown file extension ".mts" @build-core.mts

[benloh]

When testing #34, I get the following error on my intel laptop with npm run example inside the VSCode workspace terminal.

This is with a freshly cleaned node_modules folder and npm ci.

loh@clickr ursys-meme-wrapper % npm run example

> ursys@1.0.0-alpha.1 example
> npx ts-node-esm ./_ur/npm-scripts/@build-core.mts && node ./example/@build-example.mjs

TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".mts" for /Users/loh/dev/ursys-meme-wrapper/_ur/npm-scripts/@build-core.mts
    at new NodeError (node:internal/errors:405:5)
    at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:136:11)
    at defaultGetFormat (node:internal/modules/esm/get_format:182:36)
    at defaultLoad (node:internal/modules/esm/load:101:20)
    at nextLoad (node:internal/modules/esm/hooks:864:28)
    at load (/Users/loh/dev/ursys-meme-wrapper/node_modules/ts-node/dist/child/child-loader.js:19:122)
    at nextLoad (node:internal/modules/esm/hooks:864:28)
    at Hooks.load (node:internal/modules/esm/hooks:447:26)
    at MessagePort.handleMessage (node:internal/modules/esm/worker:196:24)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:786:20) {
  code: 'ERR_UNKNOWN_FILE_EXTENSION'
}

[benloh]

Fixed. The problem was that with the new PR, the existing working *.code-workspace file was not updated from the updated ursys.code-workspace-example file.