You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What package manager are you using / does the bug impact?
Yarn v1
What operating system are you using?
Linux
Describe the Bug
I am trying to run a pruned turborepo app on an Azure Linux App Service. When the server tries to start the app using 'yarn run start' I receive an error where turbo tries to import node-platform but this fails. I can see that node-platform.js exists within the folder 'node_modules/turbo/', but the binary for turbo is being called from 'node_modules/.bin/turbo'.
Expected Behavior
I would expect the app service to start as it does on a local system.
To Reproduce
Simple turborepo setup with a react app.
Github action to install, build and deploy to Azure.
Azure App service that does not try to build app, just tries to run it using the yarn version included in yarnrc and .yarn.
I am using Node 16 and Yarn 1.22.19. Turbo 1.4.3.
The text was updated successfully, but these errors were encountered:
The only way I've found around it is by specifying the full path for the turbo module. So instead of 'turbo run start', 'node ./node_modules/turbo/bin/turbo run start' works.
Seeing that this issue is quite old. I know we've changed some of the things we do to detect the binary's installation since then so I'll close this. If you're still seeing this problem, please open up a fresh issue with a reproduction with the latest canary!
What version of Turborepo are you using?
1.4.3
What package manager are you using / does the bug impact?
Yarn v1
What operating system are you using?
Linux
Describe the Bug
I am trying to run a pruned turborepo app on an Azure Linux App Service. When the server tries to start the app using 'yarn run start' I receive an error where turbo tries to import node-platform but this fails. I can see that node-platform.js exists within the folder 'node_modules/turbo/', but the binary for turbo is being called from 'node_modules/.bin/turbo'.
Expected Behavior
I would expect the app service to start as it does on a local system.
To Reproduce
I am using Node 16 and Yarn 1.22.19. Turbo 1.4.3.
The text was updated successfully, but these errors were encountered: