tailwindcss/integrations
Robin Malfait fe9fc9abba
Use resolveJsId when resolving tailwindcss/package.json (#15041)
This PR uses the `enhanced-resolve` instead of
`createRequire(…).resolve` which improves the usability when running the
upgrade tool locally using Bun.

While testing, we also noticed that it is not possible to use a
`cjs`-only plugin inside of an `esm` project. It was also not possible
to use an `esm`-only plugin inside of a `cjs` project.

# Test plan

We added integration tests in both the CLI (the CLI is an mjs project)
and in the PostCSS (where we can configure a `cjs` and `esm` PostCSS
config) integration tests where we created an `esm` and `cjs` based
project with 4 plugins (`cjs`-only, `esm`-only, and TypeScript based
plugins: `cts`-only and `mts`-only).
2024-11-19 18:39:49 +01:00
..
cli Use resolveJsId when resolving tailwindcss/package.json (#15041) 2024-11-19 18:39:49 +01:00
postcss Use resolveJsId when resolving tailwindcss/package.json (#15041) 2024-11-19 18:39:49 +01:00
upgrade Implement compat for <alpha-value> from v3 (#15033) 2024-11-19 10:01:45 -05:00
vite Vite: Don't track candidate changes for Svelte <style> tags (#14981) 2024-11-13 16:42:49 +01:00
package.json Add integration test setup and tests for the Vite integration (#14089) 2024-08-02 11:50:49 +02:00
utils.ts Improve multi-root @config linking (#15001) 2024-11-18 16:43:44 +00:00