Skip to content
This repository has been archived by the owner on Jul 10, 2022. It is now read-only.

'rm' is not recognized as an internal or external command #60

Open
ant1121 opened this issue Jan 23, 2019 · 3 comments
Open

'rm' is not recognized as an internal or external command #60

ant1121 opened this issue Jan 23, 2019 · 3 comments

Comments

@ant1121
Copy link

ant1121 commented Jan 23, 2019

I am trying to install in a Windows computer and can't get passed the npm run build command. As well your instructions say to rename the sample.env to .env but windows is preventing it. I am using a windows 8.1 OS.

@axelboc
Copy link
Owner

axelboc commented Jan 23, 2019

Hi there! You've got two options:

  • Install a bash-compliant terminal, like Cmder, instead of Windows' cmd and run the build command from there.
  • In package.json, replace rm in the prebuild script with the del command. I believe del /s /f instead of rm -Rf should to the trick.'

Let me know how you go! 😉

@ant1121
Copy link
Author

ant1121 commented Jan 26, 2019

It worked grate! thanks for the help. I still can't get the npm start or the build to see the "config/.env" the error shown is the the folder does not exist. If you have any work around would be grate as well.

@axelboc
Copy link
Owner

axelboc commented Jan 28, 2019

Hmm, perhaps the version of node you installed is too recent -- the app was built with node 6.

Rather than to downgrade it, however, you may be able to simply move the .env file to the root folder and remove the path configuration passed to the dotenv library at the top of app.js.

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

No branches or pull requests

2 participants