This repository was archived by the owner on Sep 20, 2024. It is now read-only.
Fix NODE_ENV issues for Windows users #172
Merged
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
Signed-off-by: Shyrro <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
codebender828
approved these changes
Sep 30, 2022
TylerAPfledderer
added a commit
to TylerAPfledderer/chakra-ui-vue-next
that referenced
this pull request
Oct 4, 2022
- remove 4 step in initial setup (not needed in this section) - remove mention of NODE_ENV for Windows user (was fixed in PR chakra-ui#172) - add link to `components-guide` for new component building - mention running `yarn start` before starting the playground server
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Signed-off-by: Shyrro [email protected]
Pull request checklist
Please check if your PR fulfills the following requirements:
/start features)
Pull request type
Please check the type of change your PR introduces:
What is the current behavior?
Currently, a Windows user can't use the repo out of the box, he has to do tricks to use
NODE_ENVWhat is the new behavior?
Uses cross-env so that if works everywhere
Does this introduce a breaking change?