tailwindcss/packages
Philipp Spiess 35cd2ff1ee
Resolve third-party plugins with exports in their package.json (#14775)
This PR fixes an issue when trying to resolve plugins with `exports` in
their `package.json`, like `@headlessui/tailwindcss`. The missing
`conditionNames` in the enhanced resolver config would cause it to not
properly look up the name.

## Test Plan

I added a test using the `postcss` setup (the existing plugin tests are
inside the CLI setup but the CLI can only ever run in Module JS mode).

To ensure the tests are resolving to the right environment (CJS vs MJS),
I added logging of the `import.meta.url` value to the resolver code.
When run, this was the output:

![Screenshot 2024-10-24 at
15.28.10.png](https://graphite-user-uploaded-assets-prod.s3.amazonaws.com/0Y77ilPI2WoJfMLFiAEw/c0197934-7b61-47c4-bda5-de037b31d43a.png)

Co-authored-by: Adam Wathan <adam.wathan@gmail.com>
2024-10-24 11:34:19 -04:00
..
@tailwindcss-cli Update picocolors 1.0.1 → 1.1.1 (minor) (#14771) 2024-10-24 11:25:50 +02:00
@tailwindcss-node Resolve third-party plugins with exports in their package.json (#14775) 2024-10-24 11:34:19 -04:00
@tailwindcss-postcss Prepare v4.0.0-alpha.29 release (#14761) 2024-10-23 15:30:26 +02:00
@tailwindcss-standalone Prepare v4.0.0-alpha.29 release (#14761) 2024-10-23 15:30:26 +02:00
@tailwindcss-upgrade Upgrade: Improve heuristics around important codemod (#14774) 2024-10-24 11:31:12 -04:00
@tailwindcss-vite Prepare v4.0.0-alpha.29 release (#14761) 2024-10-23 15:30:26 +02:00
internal-example-plugin Prefix internal modules with internal-* (#14074) 2024-07-29 10:58:07 -04:00
tailwindcss Ensure individual logical property utilities are sorted later than left/right pair utilities (#14777) 2024-10-24 10:58:41 -04:00
tsconfig.base.json introduce v4 codebase 2024-03-05 14:29:15 +01:00