Skip to content
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

Error when running gatsby develop #25

Closed
blessanm86 opened this issue Dec 3, 2019 · 2 comments
Closed

Error when running gatsby develop #25

blessanm86 opened this issue Dec 3, 2019 · 2 comments

Comments

@blessanm86
Copy link

When I run gatsby develop i get the error

There was an error in your GraphQL query:

The fragment "GatsbyImageSharpFluid" does not exist.

  12 |  * - `gatsby-image`: https://gatsby.dev/gatsby-image
  13 |  * - `useStaticQuery`: https://www.gatsbyjs.org/docs/use-static-query/
  14 |  */
  15 |
  16 | const Image = () => {
  17 |   const data = useStaticQuery(graphql`
  18 |     query {
  19 |       placeholderImage: file(relativePath: { eq: "gatsby-astronaut.png" }) {
  20 |         childImageSharp {
  21 |           fluid(maxWidth: 300) {
> 22 |             ...GatsbyImageSharpFluid
     |             ^^^^^^^^^^^^^^^^^^^^^^^^
  23 |           }
  24 |         }
  25 |       }
  26 |     }
  27 |   `);
  28 |
  29 |   return <Img fluid={data.placeholderImage.childImageSharp.fluid} />;
  30 | };
  31 |
  32 | export default Image;

Did you mean to use "GatsbyContentfulFluid"?

File: node_modules/@wardpeet/gatsby-plugin-static-site/e2e-tests/asset-prefix/src/components/image.js

Based on this gatsby issue I tried added e2e-tests in .npmignore and there is still an error. I just tested by directly adding the file in node_modules folder.

@wardpeet
Copy link
Owner

wardpeet commented Dec 12, 2019

Hey, i missed this issue. You don't get this error when you remove my plugin?

what version of the plugin are you using? I had some mistakes in my publish ignores. @wardpeet/[email protected] should have these things fixed

@blessanm86
Copy link
Author

@wardpeet yep installing v0.2.1 worked. thanks. closing the issue.

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

No branches or pull requests

2 participants