Bump @nuxtjs/tailwindcss from 1.4.1 to 2.1.1

[dependabot-preview]

Bumps @nuxtjs/tailwindcss from 1.4.1 to 2.1.1.

Release notes

Sourced from @nuxtjs/tailwindcss's releases.

v2.1.1

Upgrade Tailwindcss to v1.6.0

v2.1.0

Misc ✨

• Upgrade dependencies (TailwindCSS to v1.5.1).

If a new version of TailwindCSS goes out, you can always install it with npm install --save-dev tailwindcss, the module will use it directly.

Bug fixes 🐞

• Force production env for postcss on nuxt build (nuxt-modules/tailwindcss@977d605)

v2.0.0

Version 2.0 is out, including TailwindCSS v1.4 ✨

This version is a breaking change since we actually removed nuxt-purgecss dependency, since Tailwind 1.4 has a purge option now!

If you are upgrading, take a look at the new tailwind.config.js:

// tailwind.config.js
module.exports = {
  /* ... your actual config */,
  purge: {
    // Learn more on https://tailwindcss.com/docs/controlling-file-size/#removing-unused-css
    enabled: process.env.NODE_ENV === 'production',
    content: [
      'components/**/*.vue',
      'layouts/**/*.vue',
      'pages/**/*.vue',
      'plugins/**/*.js',
      'nuxt.config.js'
    ]
  }
}

Changelog

Sourced from @nuxtjs/tailwindcss's changelog.

2.1.1 (2020-07-29)

2.1.0 (2020-07-20)

Features

• use tailwind v1.4 and use purge option (#95) (09c0ee5)

Bug Fixes

• force production env for postcss on nuxt build (977d605)

Commits

• 3a8d78b chore(release): 2.1.1
• 3a35f0d chore(deps): update all non-major dependencies (#131)
• 95527a9 chore(release): 2.1.0
• 1dc2526 chore: ignore coverage on postcss
• 977d605 fix: force production env for postcss on nuxt build
• cdb2d9f chore(deps): update all non-major dependencies (#130)
• 7375ff7 chore(deps): update devdependency eslint to v7 (#103)
• 28f3488 chore(deps): update devdependency @nuxtjs/eslint-config to v3 (#106)
• 09c0ee5 feat: use tailwind v1.4 and use purge option (#95)
• c4a2e14 chore(github): issue templates
• See full diff 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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)