Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Try resolving config.default before config to ensure the config file is resolved correctly #10898

Merged
merged 4 commits into from
Mar 29, 2023

Conversation

RobinMalfait
Copy link
Contributor

@RobinMalfait RobinMalfait commented Mar 29, 2023

This PR fixes an issue where resolving the config object returns an object including default in some scenario's.

This PR tries to resolve config.default before config to ensure we always have the object we need.

Fixes: #10891

Setting this to `true` shows the output of the executed commands.
@RobinMalfait RobinMalfait merged commit a9149e4 into master Mar 29, 2023
@RobinMalfait RobinMalfait deleted the fix/issue-10891 branch March 29, 2023 13:32
bradlc added a commit to tailwindlabs/tailwindcss-intellisense that referenced this pull request Mar 29, 2023
RobinMalfait added a commit that referenced this pull request Mar 29, 2023
…ile is resolved correctly (#10898)

* try to use `config.default` before using `config`

* update changelog

* add quick `SHOW_OUTPUT` toggle for integration tests

Setting this to `true` shows the output of the executed commands.

* add integration tests for `tailwind.config.ts` and `tailwind.config.js` with ESM syntax
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

tailwind.config.ts (TypeScript) not working
1 participant