v5.0.1

• Declare export for types in package.json 2fa6eeb
• Improve README 5d750ed
• Update Github actions 21c9306

v5.0.0...v5.0.1

Drop Vue 2 support

This release updates dependencies and drops support for Vue 2.

Compatibility with Vue 2 will be maintained on version 4.*

• Prepare package.json for release f2847eb
• Merge pull request #94 from datocms/chore/drop-vue-2-support bf5902d
• Update READMEs f9a4d85
• Drop support to Vue 2 91c3f40

v4.0.7...v5.0.0

Upgrade dependencies and start using Node 20 for local development

• Upgrade default local Node version 91eccef
• Dependencies upgrade 640aa5e

v4.0.6...v4.0.7

v4.0.6

• Add support for basic link meta on Vue 2 5de3a7f
• Update README 107b3d4

v4.0.5...v4.0.6

Fix a Vue 2 compatibility issue

• Fix a StructuredText Vue 2 compatibility issue d8d56da

v4.0.4...v4.0.5

v4.0.4

• Fix rendering issue reported in issue datocms/structured-text#27 364d459
• docs: replace instance of 'react' in useSiteSearch README f862ebc
• Add a test case that includes a mailto link e82e584

v4.0.3...v4.0.4

v4.0.2

• Update lock file bd1be44
• Target EcmaScript 6, for a wider compatibility range 6e47362
• Properly limit Vue versions 7d42332
• Explicitly recommend to install Vue before installing vue-datocms 169760d
• Make Typescript happy b9db196
• Improve the search widget example 96f9132
• Refine the option type and explain why 452c50d

v4.0.1...v4.0.2

v4.0.1

• Start accepting refs beside simple arguments bb6554f

v4.0.0...v4.0.1

v4.0.0

Changes to component

You can now avoid requesting srcSet in the responsiveImage() GraphQL query, as if it's missing, the component will build it internally. This can reduce the overall GraphQL response significantly.

Basically, with v4 your responsiveImage queries can be reduced down to:

responsiveImage(imgixParams: { auto: format }) {
  src width height alt base64
}

New props for Image component:

• priority: When true, the image will be considered high priority. Lazy loading is automatically disabled, and fetchpriority="high" is added to the image. You should use the priority property on any image detected as the Largest Contentful Paint (LCP) element. It may be appropriate to have multiple priority images, as different images may be the LCP element for different viewport sizes. Should only be used when the image is visible above the fold.
• sizes: If you're using this prop, you can avoid requesting sizes in the responsiveImage() query (it will reduce the overall GraphQL response size).
• src-set-candidates: If you're not requesting srcSet in the responsiveImage() GraphQL query, src-set-candidates will be used to generate the different srcset candidate strings at various widths. Default candidates are: [0.25, 0.5, 0.75, 1, 1.5, 2, 3, 4].

Changelog

• Merge pull request #66 from datocms/dependabot/npm_and_yarn/examples/query-subscription/loader-utils-1.4.1 05da971
• Merge pull request #67 from datocms/dependabot/npm_and_yarn/examples/vue-cli-babel-javascript-vue2/loader-utils-1.4.1 2aa17b8
• Merge pull request #68 from datocms/feat/smaller-graphql-queries 64bea17
• Make Image component smarter 46b41b5
• Bump loader-utils in /examples/vue-cli-babel-javascript-vue2 6d84b7e
• Bump loader-utils from 1.4.0 to 1.4.1 in /examples/query-subscription 24e0742

v3.0.3...v4.0.0

v3.0.3

Full Changelog: v3.0.2...v3.0.3