Cross-Env is not Recognized as an Internal or External Command

Question

Good Afternoon,

I'm trying to test Experience Builder before the Developer Summit and I am having an issue.  I was able to get through the documentation for the server install.  For the client install, when I go to run npm start, I get the following:

C:\Users
athanheick\Documents\ArcGISExperienceBuilder\client>npm start

> exb-client@1.7.0 start
> cross-env NODE_ENV=development webpack --mode development --watch

'cross-env' is not recognized as an internal or external command,
operable program or batch file.

Has anyone else encountered this before?

PLadd · Answer

This was too easy of a fix but it actually worked for me at ExBDevEd 1.16.  Run in the client CMD window at the client folder.

npm install cross-env

If necessary, then run 'npm audit fix'.  Then run 'npm start'

NathanHeickLACSD · Answer

Good Morning Jennifer,

I will be honest with you.  It's been a long time since the DevSummit and I haven't used Experience Builder since then.  As best as I can remember, there were various issues related to our network settings that were making it difficult to setup at work.  It would probably take a lot of troubleshooting to figure out.  However, I believe there is an offline installation process that you can follow that works perfectly.  You can also try to do the setup on your home computer without all of the network restrictions and it will work properly.  I believe I did the offline installation at the office before going to the DevSummit and then retried the online installation at the DevSummit and it worked on the conference wi-fi.

JenniferMoczygemba1 · Answer

Hello, we are encountering this exact same issue. Any updates on how it was resolved? Thanks.