next-sanity 0.6.0 → 0.6.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +3 -3
  2. package/package.json +3 -2
package/README.md CHANGED
@@ -41,7 +41,7 @@ We have plans for optimizations in the roadmap.
41
41
 
42
42
  ## Optimizing bundle size
43
43
 
44
- The first version of `next-sanity` shipped with the [`picosanity`](https://github.com/rexxars/picosanity) client built-in. This caused some confusion for people who wants not only to pull data from their Sanity.io content lake, but also send patches and mutations via API routes. Since `picosanity` only supported fetching content, it had a smaller bundle size than the full SDK.
44
+ The first version of `next-sanity` shipped with the [`picosanity`](https://github.com/rexxars/picosanity) client built-in. This caused some confusion for people who not only want to pull data from their Sanity.io content lake, but also send patches and mutations via API routes. Since `picosanity` only supported fetching content, it had a smaller bundle size than the full SDK.
45
45
 
46
46
  You can leverage Next.js' [tree shaking](https://developers.google.com/web/fundamentals/performance/optimizing-javascript/tree-shaking) to avoid shipping unnecessary code to the browser. In order to do so, you first need to isolate the client configuration in its own file, and be sure to only use it inside of the data fetching functions (`getStaticProps`, `getServerProps`, and `getStaticPaths`) or in the function that goes into the API routes (`/pages/api/<your-serverless-function>.js`).
47
47
 
@@ -127,7 +127,7 @@ export const getClient = (usePreview) => (usePreview ? previewClient : sanityCli
127
127
 
128
128
  ## Example: Minimal blog post template
129
129
 
130
- A minimal example for a blog post template using the schema from from the Sanity Studio blog example. Includes the real-time preview using the configuration illustrated above:
130
+ A minimal example for a blog post template using the schema from the Sanity Studio blog example. It includes the real-time preview using the configuration illustrated above:
131
131
 
132
132
  ```jsx
133
133
  // pages/posts/[slug].js
@@ -246,4 +246,4 @@ $ yarn add @sanity/image-url
246
246
 
247
247
  ## License
248
248
 
249
- MIT-licensed. See LICENSE.
249
+ MIT-licensed. See [LICENSE](LICENSE).
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "next-sanity",
3
3
  "description": "Sanity.io toolkit for Next.js",
4
- "version": "0.6.0",
4
+ "version": "0.6.2",
5
5
  "author": "Sanity.io <hello@sanity.io>",
6
6
  "license": "MIT",
7
7
  "sideEffects": false,
@@ -25,7 +25,7 @@
25
25
  "coverage": "tsdx test --coverage"
26
26
  },
27
27
  "dependencies": {
28
- "@sanity/client": "^3.3.0",
28
+ "@sanity/client": "^3.3.3",
29
29
  "@sanity/groq-store": "^0.4.0",
30
30
  "groq": "^2.29.3"
31
31
  },
@@ -45,6 +45,7 @@
45
45
  "prettier": "^2.7.1",
46
46
  "react": ">=17.0.2",
47
47
  "react-dom": "^17.0.2",
48
+ "semantic-release": "^19.0.3",
48
49
  "tsdx": "^0.14.1",
49
50
  "tslib": "^2.4.0",
50
51
  "typescript": "^4.7.4"