Plugin compatibility with prereleases

[zachleat]

Both canary and beta prerelease tags have trouble in the UserConfig->versionCheck method.

Normal version checking approach: https://github.com/11ty/eleventy-navigation/blob/fccb334e0d7cad363bda691178cb53e35ee79981/package.json#L35 and https://github.com/11ty/eleventy-navigation/blob/fccb334e0d7cad363bda691178cb53e35ee79981/.eleventy.js#L6

Related 11ty/eleventy-plugin-rss#28

We need to use the includePrerelease option to include these:

• https://docs.npmjs.com/cli/v6/using-npm/semver#prerelease-tags
• https://www.npmjs.com/package/semver

This will ship in 1.0.0-beta.2

[zachleat]

For now existing plugins will need to keep the canary check in place to keep compatibility with the canary tag, as canary versions of Eleventy will not have this includePrelease option enabled.

"11ty": {
  "compatibility": ">=0.7 || >=1.0.0-canary"
},

Once folks are on the beta tag we can get rid of it moving forward (and of course we needn’t add a || >= 1.0.0-beta check either as this will be solved in 1.0.0-beta.2 core)

[zachleat]

We’ll probably want to ship 1.0.0-beta.2 soon so that folks don’t run into this.

[zachleat]

1.0.0-beta.2 has shipped.

[zachleat]

Review of core plugin compatibility checks, need to remove peerDependencies entry and move instead to 11ty.compatibility method in package.json:

• eleventy-navigation
• eleventy-plugin-rss Update eleventy peer dependency eleventy-plugin-rss#28
• eleventy-plugin-syntaxhighlight Switch from peerDependencies to 11ty.compatibility eleventy-plugin-syntaxhighlight#62
• eleventy-plugin-vue
• eleventy-plugin-inclusive-language

Not applicable, do not need peerDependencies: eleventy-img, eleventy-cache-assets