-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] = temporal-delivery-app initialization: Error: ENOENT: no such file or directory tsconfig.json
#251
Comments
Error: ENOENT: no such file or directory tsconfig.json
Hey, thanks for reporting and including your Node version! I had only tested it in Node 16, but now I'm reproducing your error in 17 and 18. Looking into it now. In the meantime, Node 16 should work. |
@lorensr While this is fixed in the sdk-typescript repository it doesn't look like the @temporal/create package has been published in a long time. Last version (1.6.0) was published two months ago. I came across this same bug trying to create the monorepos sample after the webinar today. |
Sorry about that! For now, you can clone this repo and cd into food-delivery |
I ended up cloning the sdk-typescript package and running the cli.js file from main because I was curious about the bug. Which led me to another thought. It appears the fix for it is to just ignore the error if tsconfig.json doesn't exist. But, for example in the monorepo-folders sample, it would need to check that packages folder and then do the node version replacing in each of them for that part of the code to work correctly (I had just skimmed it). If the intent is to change the |
Fixed in temporalio/sdk-typescript#1089. Thanks @jhubbardsf. |
What are you really trying to do?
I am attempting to follow the Temporal NodeJS delivery app guide from this blogpost: Building Reliable Distributed Systems in Node.js
Describe the bug
After running the first command specified in the tutorial, I am getting an error:
Minimal Reproduction
1.Attempt to initialize the delivery app example using the following command used in the blog post:
Environment/Versions
References
The text was updated successfully, but these errors were encountered: