-
Notifications
You must be signed in to change notification settings - Fork 0
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
[Snyk] Fix for 1 vulnerabilities #12
Open
pradsir
wants to merge
1
commit into
main
Choose a base branch
from
snyk-fix-ed9aad71d1342566d53bd4b79eb65c01
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-FILETYPE-2958042
Gatsby Cloud Build Report🚩 Your build failed. See the build logs here Errors Your plugins must export known APIs from their gatsby-node.js. See https://www.gatsbyjs.org/docs/node-apis/ for the list of Gatsby node APIs. - The plugin gatsby-plugin-sharp@3.13.0 is using the API "pluginOptionsSchema" which was introduced in gatsby@2.25.0. - The plugin gatsby-source-filesystem@2.6.0 is using the API "pluginOptionsSchema" which was introduced in gatsby@2.25.0. Some of the following may help fix the error(s): - npm install gatsby@^2.25.0 "gatsby-source-cosmicjs" threw an error while running the sourceNodes lifecycle: Request failed with status code 404 There was an error in your GraphQL query: Cannot query field "allCosmicjsPosts" on type "Query". If you don't expect "allCosmicjsPosts" to exist on the type "Query" it is most likely a typo. However, if you expect "allCosmicjsPosts" to exist there are a couple of solutions to common problems: - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have - You want to optionally use your field "allCosmicjsPosts" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "Query": https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions "gatsby-node.js" threw an error while running the createPages lifecycle: Cannot read property 'allCosmicjsPosts' of undefined 34 | 35 | // Create blog posts pages. > 36 | const posts = result.data.allCosmicjsPosts.edges; | ^ 37 | 38 | each(posts, (post, index) => { 39 | const next = index === posts.length - 1 ? null : posts[index + 1].node; There was an error in your GraphQL query: Cannot query field "cosmicjsSettings" on type "Query". If you don't expect "cosmicjsSettings" to exist on the type "Query" it is most likely a typo. However, if you expect "cosmicjsSettings" to exist there are a couple of solutions to common problems: - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have - You want to optionally use your field "cosmicjsSettings" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "Query": https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions There was an error in your GraphQL query: Cannot query field "allCosmicjsPosts" on type "Query". If you don't expect "allCosmicjsPosts" to exist on the type "Query" it is most likely a typo. However, if you expect "allCosmicjsPosts" to exist there are a couple of solutions to common problems: - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have - You want to optionally use your field "allCosmicjsPosts" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "Query": https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions There was an error in your GraphQL query: Cannot query field "cosmicjsSettings" on type "Query". If you don't expect "cosmicjsSettings" to exist on the type "Query" it is most likely a typo. However, if you expect "cosmicjsSettings" to exist there are a couple of solutions to common problems: - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have - You want to optionally use your field "cosmicjsSettings" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "Query": https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions There was an error in your GraphQL query: Cannot query field "cosmicjsPosts" on type "Query". If you don't expect "cosmicjsPosts" to exist on the type "Query" it is most likely a typo. However, if you expect "cosmicjsPosts" to exist there are a couple of solutions to common problems: - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have - You want to optionally use your field "cosmicjsPosts" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "Query": https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions There was an error in your GraphQL query: Cannot query field "cosmicjsSettings" on type "Query". If you don't expect "cosmicjsSettings" to exist on the type "Query" it is most likely a typo. However, if you expect "cosmicjsSettings" to exist there are a couple of solutions to common problems: - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have - You want to optionally use your field "cosmicjsSettings" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "Query": https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions |
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.
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.
Changes included in this PR
Vulnerabilities that will be fixed
With an upgrade:
Why? Recently disclosed, Has a fix available, CVSS 7.5
SNYK-JS-FILETYPE-2958042
(*) Note that the real score may have changed since the PR was raised.
Commit messages
Package name: gatsby-plugin-sharp
The new version differs by 250 commits.See the full diff
Package name: gatsby-source-filesystem
The new version differs by 250 commits.See the full diff
Check the changes in this PR to ensure they won't cause issues with your project.
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.