fix: other postcss plugins should not run before tailwindcss (#38)

Maybe like the example in [tailwindcss
documentation](https://v3.tailwindcss.com/docs/installation/using-postcss),
the tailwindcss postcss plugin should in the first place:
```js
module.exports = {
  plugins: {
    tailwindcss: {},
    autoprefixer: {},
  }
}
```

Author: luhc228

.github/workflows/release.yml

@@ -21,7 +21,7 @@ jobs:
         uses: actions/checkout@v4
 
       - name: Install Pnpm
-        run: corepack enable
+        run: npm i -g corepack@latest --force && corepack enable
 
       - name: Setup Node.js
         uses: actions/setup-node@v4

.github/workflows/test.yml

@@ -28,7 +28,7 @@ jobs:
         uses: actions/checkout@v4
 
       - name: Install Pnpm
-        run: corepack enable
+        run: npm i -g corepack@latest --force && corepack enable
 
       - name: Setup Node.js
         uses: actions/setup-node@v4

CHANGELOG.md

@@ -0,0 +1,5 @@
+# CHANGELOG
+
+## 0.2.0
+
+- Fixed bug that other postcss plugins should not run before tailwindcss.

src/TailwindCSSRspackPlugin.ts

@@ -260,12 +260,12 @@ class TailwindRspackPluginImpl {
               ]);
 
               const processor = postcss([
-                ...(options.postcssOptions?.plugins ?? []),
                 // We use a config path to avoid performance issue of TailwindCSS
                 // See: https://github.com/tailwindlabs/tailwindcss/issues/14229
                 tailwindcss({
                   config: configPath,
                 }),
+                ...(options.postcssOptions?.plugins ?? []),
               ]);
 
               TailwindRspackPluginImpl.#postcssProcessorCache.set(entryName, [