gatsby-codemods
Advanced tools
Comparing version 1.0.0-beta.1 to 1.0.0-beta.2
@@ -6,2 +6,8 @@ # Change Log | ||
<a name="1.0.0-beta.2"></a> | ||
# [1.0.0-beta.2](https://github.com/gatsbyjs/gatsby/compare/gatsby-codemods@1.0.0-beta.1...gatsby-codemods@1.0.0-beta.2) (2018-08-13) | ||
**Note:** Version bump only for package gatsby-codemods | ||
<a name="1.0.0-beta.1"></a> | ||
@@ -8,0 +14,0 @@ |
{ | ||
"name": "gatsby-codemods", | ||
"version": "1.0.0-beta.1", | ||
"version": "1.0.0-beta.2", | ||
"description": "Stub description for gatsby-codemods", | ||
@@ -34,3 +34,3 @@ "main": "index.js", | ||
}, | ||
"gitHead": "48a2d7e4f9d3a18d5e275a9b7e7d628b3caaf86d" | ||
"gitHead": "c666749b4bac1a676647623102bff5323223ba8a" | ||
} |
@@ -42,4 +42,6 @@ ## gatsby-codemods | ||
Add `import { graphql } from "gatsby"` to files that have graphql queries in them. See the [Gatsby v2 migration guide for more details].(https://next.gatsbyjs.org/docs/migrating-from-v1-to-v2/#import-graphql-from-gatsby) | ||
Add a `graphql` import to modules that use the `graphql` tag function without an import. This was supported in Gatsby v1 and deprecated for Gatsby v2. | ||
See the [Gatsby v2 migration guide for details on when to use this](https://next.gatsbyjs.org/docs/migrating-from-v1-to-v2/#import-graphql-from-gatsby). | ||
```sh | ||
@@ -49,2 +51,23 @@ jscodeshift -t node_modules/gatsby-codemods/dist/transforms/global-graphql-calls.js <path> | ||
Example result: | ||
```diff | ||
import React from "react" | ||
+ import { graphql } from "gatsby" | ||
export default ({ data }) => ( | ||
<h1>{data.site.siteMetadata.title}</h1> | ||
) | ||
export const query = graphql` | ||
query { | ||
site { | ||
siteMetadata { | ||
title | ||
} | ||
} | ||
} | ||
` | ||
``` | ||
### More scripts | ||
@@ -51,0 +74,0 @@ |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
11408
76
1