Skip to content
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

'ENGINE' is not recognized as an internal or external command #136

Open
AjayTiwari-Al opened this issue Jul 25, 2022 · 1 comment
Open

Comments

@AjayTiwari-Al
Copy link

image

Hello,

I need assistance on the following error.
I have installed all the dependencies & also setup the AWS credential.
Was facing some issues with proxy while installing npm install but got resolved after some workaround
Now when I try to run the npm run start-babylon I am getting an error as engine is not recognized by internal or external command as shown in figure.

@brhook-aws
Copy link
Contributor

cross-env should allow Windows machine to compile the variable setting here. It is a dependency from our package and in the package.json for the building of the Babylon package, as seen here.

Can you confirm which operating machine you are on, and that you are on the latest commit of the package's mainline2.0 branch? Finally, for the package.json file, please confirm that the start-babylon commands looks like cross-env ENGINE=babylon NODE_ENV=development webpack-dev-server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants