Skip to content

feat: Add cross-env to project scripts #672

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

Merged
merged 1 commit into from
Feb 25, 2021

Conversation

cynthi8
Copy link
Contributor

@cynthi8 cynthi8 commented Feb 24, 2021

cross-env allows Windows users to run npm scripts that set environmental
variables. Single quotes were also replaced with escaped double quotes
for Windows compatibility.

  • What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
  • Bug fix
  • Feature implementation
  • What changes have you introduced?
    cross-env module added and scripts in package.json have been updated to work under Windows. Fixes Error running dev setup on Windows #663

  • Does this PR introduce a breaking change?
    No. For development, npm install will need to be rerun to install the new cross-env dependency though.

  • Preview / Steps to verify your work:
    npm start now works to begin the application on Windows 10 with both Powershell and CMD. Scripts still work under Linux.

cross-env allows Windows users to run npm scripts that set enviromental
variables. Single quotes were also replaced with escaped double quotes
for Windows compatibility.
@orangecms orangecms merged commit 2a7f356 into fossasia:development Feb 25, 2021
@orangecms
Copy link
Collaborator

Awesome, thank you! :)

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

Successfully merging this pull request may close these issues.

Error running dev setup on Windows
2 participants