Error while building types

[ryderwishart]

To Reproduce
Steps to reproduce the behavior:

1. clone repo
2. npm i
3. npm run build:types
4. See error:

> build:types
> cd lib/papi-dts && npm run build


> [email protected] build
> tsc && prettier --write papi.d.ts && ts-node edit-papi-d-ts.ts && prettier --write papi.d.ts

[warn] Ignored unknown option { tsdoc: true }.
papi.d.ts 287ms (unchanged)
TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for /Users/ryderwishart/paranext-core/lib/papi-dts/edit-papi-d-ts.ts
    at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:160:9)
    at defaultGetFormat (node:internal/modules/esm/get_format:203:36)
    at defaultLoad (node:internal/modules/esm/load:143:22)
    at async nextLoad (node:internal/modules/esm/hooks:750:22)
    at async nextLoad (node:internal/modules/esm/hooks:750:22)
    at async Hooks.load (node:internal/modules/esm/hooks:383:20)
    at async handleMessage (node:internal/modules/esm/worker:199:18) {
  code: 'ERR_UNKNOWN_FILE_EXTENSION'
}

I'm running on a Mac M1.

[lyonsil]

Hey @ryderwishart , sorry for the trouble. This is a known issue with ts-node right now. It's mentioned in our troubleshooting guide on the wiki.

One thing to note about Macs is that the platform will run overall, but the .NET process won't do much for you yet. If you're on Discord, I know you can ask @jolierabideau for tips as she also has been doing dev work on her Mac.

[tjcouch-sil]

Decided to go ahead and work on updating to Node LTS v20.11.1 :)
Updated to node 20.11.1 LTS, replaced ts-node with tsx in the necessary places as a temporary fix for https://github.com/TypeStrong/ts-node/issues/1997 by tjcouch-sil · Pull Request #778 · paranext/paranext-core
Updated to node 20.11.1 LTS by tjcouch-sil · Pull Request #64 · paranext/paranext-extension-template
Updated to node 20.11.1 LTS by tjcouch-sil · Pull Request #12 · paranext/paranext-multi-extension-template

[ryderwishart]

I was able to start the app, thanks @tjcouch-sil for the quick fix!!

One thing to note about Macs is that the platform will run overall, but the .NET process won't do much for you yet.

@lyonsil, can you help me understand this better? I don't have any context or idea of what this means, except that I can see that the app is failing to parse John 11:35 apparently (unless that's just some default content in there at the moment and it's not actually trying to parse anything).

[lyonsil]

@ryderwishart The .NET process is our way of getting to Paratext resources. Those resources are currently the only way to get scripture data in the platform.

If you want to read all the low level details about what problems we're having see #264 . At a high level, Unicode (ICU) libraries on macOS are not the same as what we have on Linux and Windows. A part-time volunteer who is familiar with development on Macs is working on the problem. Until the issue is resolved, everything except scripture access should be working, but that is obviously a big hole.

If you have some straightforward APIs or other ways of getting scripture data, then perhaps this isn't a big blocker for you. As a desktop application for translators who are working on local projects, we know this has to be resolved if they are going to be able to use Macs. For developers, though, there are other ways around this if you have other APIs you're using.

If you'd like to talk about this in more detail please feel free to reach out on Discord or email and we can have a longer discussion or video chat.