fix: use css imports instead of separate postcss processing of each file

[Theiaz]

Description
Instead of merging css files by npm scripts a better way would be to use @import inside css files.

I've also unminimized the atom-one-dark.min.css, because it should be human readable. Minification should only be done for main.min.css files which is the only included css file.

Related issue(s)
fixes #157
fixes #158

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[derberg]

@Theiaz why tailwind.min.css is removed? is it covered by https://github.com/asyncapi/html-template/pull/159/files#diff-05ed1c7f99e45b485708115502a1e0f28c8547e9a9a29c1b8664f79103cf7873R4 ?

[Theiaz]

Separate css file for tailwind styles like tailwind.min.css is not necessary. As you can see in main.min.css all the needed utility classes of tailwind are generated (like px-2, text-gray-100, ...).

This is because of the @tailwind base/components/utility directives inside main.css (see here). Tailwind scannes the css class declarations inside the html files. Files which needs to be be scanned are declared inside tailwind.config.js.

module.exports = {
  purge: ["./template/**/*.html", "./partials/**/*.html"], 
  ...
}

Tailwind then automatically wires the necessary style inside main.css. The resulting css file has the following structure:

/* atom-dark theme */
/* tailwind utility classes */
/* custom css declared after @tailwind utilities; */

[derberg]

@Theiaz perfect, thanks for the patience and detailed explanation 🙏🏼

[asyncapi-bot]

🎉 This PR is included in version 0.18.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀