TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts"
how do I get rid of that error, using the Get started template with TS
Shttps://github.com/apify/crawlee/issues/1966 nvm found that
GitHub
ts-node-esm is broken in node v20+ (tested on v20.4), we should move to node --no-warnings=ExperimentalWarning --loader ts-node/esm src/main.ts before it's fixed. > ts-node-esm -T src/main.t...
CI think I am experiencing this bug as well and thus can't start the crawlee project 
. I have updated to the latest node and tsc-node-esm so far I can see. Do you have any workarounds to this?
. I have updated to the latest node and tsc-node-esm so far I can see. Do you have any workarounds to this?C@Lukas Krivka Do you have any idea about this issue? 
Vyeah tsc has been a pain in the ass with .ts files, either use tsx or simply .js files in the meanwhile
Vtsc needs to fix their esm bundling
C@AltairSama2 tsx works locally but is not supported on apify cloud so my customers cant start the actor 
Vthen the workaround is to use
.jsatleast according to tsx's github last I checked
R@Casper it IS supported on the platfrom - I started to experience this too recently, and using instaed of
ts-node
CThanks for the confirmation. I finally resolved the issues 
CHowever I have also updated my Readme file but my actor on the apify store has not been updated with the changes to my readme file. How can I figure out why this has failed?
Also I have fixed a bunch of bugs that put the actor into maintenance mode, but when I remove it from maintenance mode, Apify automated testing system keeps setting it back and reference a previous test as the reason.
Also I have fixed a bunch of bugs that put the actor into maintenance mode, but when I remove it from maintenance mode, Apify automated testing system keeps setting it back and reference a previous test as the reason.
R@Zuzka (Apify)