au run fails when the app wasn't generated by that PC.

I’m submitting a bug report

• Library Version: major

Please tell us about your environment:

• Operating System: Windows [10]
• Node Version: 4.4.7
• NPM Version: 3.8.9
• Language: ESNext

Current behavior: When uploading a repo to GitHub, I ignore node_modules as usual. When pulling the project, followed by: npm install && au run It will lead with an error and won’t run. The only way I found to get the app to work is by using au new to generate a new project and then replacing the SRC files…

• What is the expected behavior? To run
• What is the motivation / use case for changing the behavior? logic

[jaeko44]

@EisenbergEffect People are still running into issues here so i think this should be re-oppened. The NPM issue was fixed by the latest NPM. However moving from Ubuntu -> Windows, Mac -> Windows or the opposite causes issues. As seen above.

This is mainly caused by aurelia.json’s not being able to read ‘/’ in windows, and ’ \ \ ’ in Mac/Linux.

[alexisargyris]

@jaeko44 I’m afraid it didn’t work:

• I’m on npm 3.10.6,
• did (once again) a ‘npm install’,
• replaced in aurelia.json all occurences of ‘/’ (Mac) with ‘\’ (Win)

and I still get exactly the same errors. Am I doing something wrong? Is there any other idea?

Meantime, I’ll try next to install in a clean directory to see if that will make any difference.

[later]

Yes, a clean installation worked! So here’s a possible checklist of things currently necessary when moving from Mac to Win:

• latest npm (i.e. npm install -g npm)
• latest aurelia-cli (i.e. npm install aurelia-cli -g). In my case this failed for some reason so I had to remove the directory manually and re-install).
• latest app source files in a clean directory
• replace in aurelia_project/aurelia.json all occurences of ‘/’ (Mac) with ‘\’ (Win) as suggested by @jaeko44 above