fix(examples): avoid warning with legacy postcss.config.js

[mercs600]

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Resolves: #7062 . Just removed outdated postcss.config.js and setup postcss plugins in nuxt.config.js.

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly. (PR: #)
• I have added tests to cover my changes (if not applicable, please state why)
• All new and existing tests are passing.

[codecov-io]

Codecov Report

Merging #7098 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #7098   +/-   ##
=======================================
  Coverage   62.69%   62.69%           
=======================================
  Files          84       84           
  Lines        3394     3394           
  Branches      926      926           
=======================================
  Hits         2128     2128           
  Misses       1018     1018           
  Partials      248      248

Flag	Coverage Δ
#unittests	62.69% <ø> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c8e7397...1780f27. Read the comment docs.

[manniL]

Thank you! ☺️

I guess an update with https://github.com/nuxt-community/nuxt-tailwindcss would be even better 😋

[mercs600]

@manniL So you want to change this example to '@nuxtjs/tailwindcss' module ? I can do it, but is it worthy ? I mean setup the module is nothing special, but this simple configuration shows to developers how they can do it by hand - it gives more values. What do you think ?

[pi0]

Hi @mercs600 thanks for PR ❤️ I was also going to comment the same as @manniL. Let's wait for @atinux opinion on this :)