ERR_UNKNOWN_FILE_EXTENSION on Node v20.0.0 #1961
Replies: 3 comments 4 replies
-
You need to use |
Beta Was this translation helpful? Give feedback.
-
You'll need to tell the node binary to stop requiring extensions. Currently this is done through an experimental flag, --experimental-specifier-resolution=node. Then you can use ts-node as a loader instead 👇 "start:dev": "node --no-warnings=ExperimentalWarning --experimental-specifier-resolution=node --loader ts-node/esm/transpile-only src/main.ts", |
Beta Was this translation helpful? Give feedback.
-
Closing this as it seems that @B4nan already solved it on #1966 |
Beta Was this translation helpful? Give feedback.
-
Hey all,
I'm starting to learn about Crawlee and started following the "Quick start guide". Unfortunately, I had problems to run the example because of an error with TS. So just for let you all know about this and to know that this comment on ts-node issues helped me to make it run, in case some of you also have problems. I haven't read a lot about the workaround, if it's safe, etc. because I'm just learning right now for curiosity, but if someone does want to read more about this and probably make a PR to Crawlee's docs, it might help more people as well.
Beta Was this translation helpful? Give feedback.
All reactions