This repository was archived by the owner on Sep 12, 2020. It is now read-only.
Using .env on windows for set up NODE_ENV=development with npm start - #26
Open
jsheperd wants to merge 1 commit into
Open
Using .env on windows for set up NODE_ENV=development with npm start#26jsheperd wants to merge 1 commit into
jsheperd wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It is difficult for beginners to manage NODE_ENV environment variable on windows. I have found it much easier to use 'npm start' instead of manage NODE_ENV from the command line. The change worked well on windows, it should be fine on linux too.