Bump @11ty/eleventy from 0.11.1 to 2.0.0

[dependabot]

Bumps @11ty/eleventy from 0.11.1 to 2.0.0.

Release notes

Sourced from @​11ty/eleventy's releases.

Eleventy v2.0.0-beta.2

The first bug-fix follow up to the long awaited 2.0.0-beta.1.

Features

• Adds eleventy.env.runMode to global data. #2770

Bug Fixes

• Fix for Plugin Compatibility Checks on Vite and WebC plugins. #2758
• Fix a large number of issues requiring dev server restart to see content updates. #2773 #2755
• Use eleventy-dev-server@1.0.3 (fixes domDiff option): 11ty/eleventy-dev-server#48

Housekeeping

Full Changelog: 11ty/eleventy@v2.0.0-beta.1...v2.0.0-beta.2

Eleventy v1.0.2: One bug fix for Liquid Shortcode Argument Parsing

Eleventy v1.0.2 🎈🐀⚡️🕚

• Full docs for v1.0.2 on our web site

This project would not be possible without our lovely community. Thank you to everyone that built something with Eleventy (×595 authors on our web site!), wrote a blog post about Eleventy, contributed code to core or plugins, documentation, asked questions, answered questions, braved The Leaderboards, participated on Discord, filed issues, attended (or organized!) a meetup, said a kind word on Twitter ❤️.

• 🏆 A super special thanks to Peter DeHaan for their tireless contributions on the Eleventy Issue tracker.
• All of our supporters on Open Collective ❤️
  • Gold Sponsors: Sanity.io, Nordhealth, CloudCannon and Silver Sponsors: Set Creative Studio, Unabridged Software, PQINA, The Coders Guild, Bejamas, Nathan Smith, Flatirons Development, Monarch Air Group, Ben Nash, getform.io, OCEG, Mercury Jets
  • A full list of Backers can be found below!
• Contribute on Open Collective
• How else can you contribute to Eleventy?

Install or Upgrade

• Install to your local project: npm install @11ty/eleventy
• Already installed in your local project? Upgrade your version: npm update @11ty/eleventy
• Read more about local project versus global installation

Features

• Fixes for liquid argument parsing on shortcodes #2154 #2348 #2367 #2369
  • Help from @​epelc @​lexoyo @​denisenadal @​mahnunchik @​harttle

Milestone

All bug fix issues can be perused at the GitHub milestone: https://github.com/11ty/eleventy/milestone/39?closed=1

Major Version Dependency Upgrades

There are no major version dependency updates between 1.0.2 and 1.0.1.

... (truncated)

Changelog

Sourced from @​11ty/eleventy's changelog.

Dependency notes

• @iarna/toml has a 3.0 that we have never been on but it was released the same day as the last 2.x https://github.com/BinaryMuse/toml-node/commits/master (needs more investigation)

List of dependencies that went ESM

• @sindresorhus/slugify ESM at 2.x
• multimatch is ESM at 6
• bcp-47-normalize at 1.x

Release Procedure

1. (Optional) Update minor dependencies in package.json
   • npx npm-check-updates
   • or npm outdated + npm update --save
2. If the minimum Node version changed, make sure you update package.json engines property.
   • Make sure the error message works correctly for Node versions less than 10.
     • 0.12.x+ requires Node 10+
     • 1.x+ requires Node 12+
     • 2.x+ requires Node 14+
3. rm -rf node_modules && rm -f package-lock.json && npm install
4. npm audit
5. Make sure npx ava runs okay
6. Update version in package.json
   • (Canary) Use -canary.1 suffix
   • (Beta) Use -beta.1 suffix
7. Run npm run coverage
8. Check it all in and commit
9. Tag new version
10. Release
    • (Canary) npm publish --access=public --tag=canary
      • NOTE: that in 3.0 we need to switch this to alpha to avoid 11ty/eleventy#2758
    • (Beta) npm publish --access=public --tag=beta
      • NOTE: When releasing a beta, make sure to also release a canary to mitigate 11ty/eleventy#2758.
    • (Main) npm publish --access=public
11. (Optional) Build and commit a new the eleventy-edge-cdn project to generate a new Eleventy Edge lib.

Unfortunate note about npm canary tag: if you push a 1.0.0-canary.x to canary after a 2.0.0-canary.x, it will use the last pushed tag when you npm install from canary (not the highest version number)

Docs/Website (Main releases only)

1. Maybe search for 2.0.0-canary. or 2.0.0-beta. in the docs copy to update to the stable release, if applicable.
2. Check in a new 11ty-website site with updated package.json version.
3. Add version to 11ty-website versions.json
4. Commit it
5. Create a new branch for branched version
6. (Main) Check out the previous version git branch and add outdated: true to _data/config.json and commit/push.
7. Go to https://app.netlify.com/sites/11ty/settings/domain and set up a subdomain for it.

Release Notes on GitHub (Main releases only)

... (truncated)

Commits

• 05c6263 v2.0.0
• 5c2a5bf Update dev-dependencies
• 7ed1fef Merge pull request #2781 from danburzo/mdlib-set
• 97243b6 v2.0.0-beta.3
• 55e0a62 v2.0.0-canary.35
• 23b80d9 Merge pull request #2783 from mrmartineau/fix/serverless-var
• 9f13b8e Fixes serverlessFilePath is not defined (2.0.0-beta.2) #2782
• b466258 Make markdown library .set() method optional
• bde84b4 v2.0.0-beta.2
• 6f877de v2.0.0-canary.34
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)