Skip to content

docs: how to run on windows locally #1177

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 2 commits into from
Jul 1, 2024
Merged

Conversation

andrewnessinjim
Copy link
Contributor

The syntax for setting env variables is different for powershell and command prompt, so I have mentioned only the command prompt syntax to keep it simple. I think it's sufficient if Windows users just know the syntax needs to be updated.

We could add the windows syntax for setting GATSBY_CONTENT_ALLOW and GATSBY_CONTENT_IGNORE too, but it feels like an overkill.

Tested by changing the syntax in package.json file:
image

Closes #1172

@andrewnessinjim andrewnessinjim requested a review from a team as a code owner June 26, 2024 18:38
@andrewnessinjim
Copy link
Contributor Author

I updated the commit message to have "docs" prefix instead of "feat" and forced pushed the commit.

@andrewnessinjim
Copy link
Contributor Author

I tested the command:
image

@wraithgar wraithgar changed the title feat: how to run on windows locally docs: how to run on windows locally Jul 1, 2024
@wraithgar wraithgar merged commit 0a0a3a1 into npm:main Jul 1, 2024
8 of 9 checks passed
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.

Using cross-env for cross platform compatibility
2 participants