typescript error

[choudhryfrompak]

i am getting this error when trying to run yarn dev, i have tried reinstalling ts-node but didnt worked for me

node ./src/index.ts src/index.ts
TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for C:\Users\PAC-GPT\Pictures\deployed-version\src\index.ts
at new NodeError (node:internal/errors:405:5)
at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:99:9)
at defaultGetFormat (node:internal/modules/esm/get_format:142:36)
at defaultLoad (node:internal/modules/esm/load:86:20)
at nextLoad (node:internal/modules/esm/hooks:726:28)
at load (C:\Users\PAC-GPT\Pictures\deployed-version\node_modules\ts-node\dist\child\child-loader.js:19:122)
at nextLoad (node:internal/modules/esm/hooks:726:28)
at Hooks.load (node:internal/modules/esm/hooks:370:26)
at MessagePort.handleMessage (node:internal/modules/esm/worker:168:24)
at [nodejs.internal.kHybridDispatch] (node:internal/event_target:762:20) {
code: 'ERR_UNKNOWN_FILE_EXTENSION'
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
[nodemon] app crashed - waiting for file changes before starting...

[Luisotee]

Can you write here the whole log after you enter yarn dev?

[choudhryfrompak]

it is fixed after running a command :
sudo apt install libatk1.0-0
sudo apt install libgtk-3-0 libgbm-dev libnss3 libxss1 libasound2

Thanks for support waiting for new features.

[veigamann]

Which Node version did you use when you first got the error?

[choudhryfrompak]

i used the suggested version that was mentioned in start.sh file

…

On Thu, Jul 6, 2023, 5:27 AM Matheus Veiga ***@***.***> wrote: Which Node version did you use when you first got the error? — Reply to this email directly, view it on GitHub <#86 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A64GURCKONRMXLFKWH63ETLXOYA53ANCNFSM6AAAAAAZW6PGBU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[MikeBivins]

This does occur again when using latest nodejs (20.5.xxxx i believe) . Simply downgrading works for me right now. If theres still someone experiencing the same today in late august.

[veigamann]

I haven't tried it with newer Node versions yet. For now, just stick to the LTS or 18.15.0, as mentioned in the prerequisites section of the readme. I'll keep an eye out and work on compatibility with newer versions. Thanks for bringing this up! Closing this issue as Node 18.15.0 works fine.