Don't publish examples to npm #31
Merged
Conversation
This file contains 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
|
Thanks @sidharthachatterjee! We usually use |
|
Thank you for the quick response, @Haroenv! I've removed |
sidharthachatterjee
changed the title
|
published 0.3.1 with this :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As of
[email protected](gatsbyjs/gatsby#15284), we now parse GraphQL queries in dependencies to enable packages to ship queries!The examples in this repo however interfere with this and cause this package to break (details in gatsbyjs/gatsby#15344)
We highly recommend not shipping examples to
npmand this PR fixes this by adding it to .npmignoreCheers from the gatsby team!