@sanity/client 3.4.0-beta.esm.4 → 3.4.0

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 (13) hide show
  1. package/README.md +1 -1
  2. package/dist/sanityClient.browser.mjs +316 -3452
  3. package/dist/sanityClient.browser.mjs.map +3 -3
  4. package/lib/config.js +2 -2
  5. package/lib/generateHelpUrl.js +7 -0
  6. package/lib/sanityClient.js +5 -1
  7. package/lib/warnings.js +1 -1
  8. package/package.json +18 -29
  9. package/sanityClient.d.ts +252 -97
  10. package/umd/sanityClient.js +30 -30
  11. package/umd/sanityClient.min.js +1 -1
  12. package/dist/sanityClient.node.cjs +0 -1232
  13. package/dist/sanityClient.node.cjs.map +0 -7
package/README.md CHANGED
@@ -37,7 +37,7 @@ Initializes a new Sanity Client. Required options are `projectId`, `dataset`, an
37
37
 
38
38
  Sanity uses ISO dates (YYYY-MM-DD) in UTC timezone for versioning. The explanation for this can be found [in the documentation](http://sanity.io/docs/api-versioning)
39
39
 
40
- In general, unless you know what API version you want to use, you'll want to set it to today's UTC date. By doing this, you'll get all the latest bugfixes and features, while locking the API to prevent breaking changes.
40
+ In general, unless you know what API version you want to use, you'll want to statically set it to today's UTC date when starting a new project. By doing this, you'll get all the latest bugfixes and features, while locking the API to prevent breaking changes.
41
41
 
42
42
  **Note**: Do not be tempted to use a dynamic value for the `apiVersion`. The reason for setting a static value is to prevent unexpected, breaking changes.
43
43