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

[Bug] Relative paths in tailwind.config.js not always working #57

Closed
marklawlor opened this issue May 23, 2022 · 5 comments
Closed

[Bug] Relative paths in tailwind.config.js not always working #57

marklawlor opened this issue May 23, 2022 · 5 comments

Comments

@marklawlor
Copy link
Collaborator

There are still some issues with using relative content in tailwind.config.js

The current workaround is using absolute paths

module.exports = {
  content: [
    `${__dirname}/code.{js,ts,jsx,tsx}`,
  ],
};
@marklawlor
Copy link
Collaborator Author

Keeping this open until deployed

github-actions bot pushed a commit that referenced this issue May 25, 2022
# [1.5.0-next.12](v1.5.0-next.11...v1.5.0-next.12) (2022-05-25)

### Bug Fixes

* allow absolute paths to tailwind config ([0421a91](0421a91))
* better matching with relative content paths in tailwind.config.js ([f99bc1f](f99bc1f)), closes [#57](#57)
@github-actions
Copy link
Contributor

🎉 This issue has been resolved in version 1.5.0-next.12 🎉

The release is available on:

Your semantic-release bot 📦🚀

github-actions bot pushed a commit that referenced this issue May 27, 2022
## [1.4.5](v1.4.4...v1.4.5) (2022-05-27)

### Bug Fixes

* better matching with relative content paths in tailwind.config.js ([fd43261](fd43261)), closes [#57](#57)
@github-actions
Copy link
Contributor

🎉 This issue has been resolved in version 1.4.5 🎉

The release is available on:

Your semantic-release bot 📦🚀

github-actions bot pushed a commit that referenced this issue May 27, 2022
# [1.5.0-next.19](v1.5.0-next.18...v1.5.0-next.19) (2022-05-27)

### Bug Fixes

* better matching with relative content paths in tailwind.config.js ([fd43261](fd43261)), closes [#57](#57)
@github-actions
Copy link
Contributor

🎉 This issue has been resolved in version 1.5.0-next.19 🎉

The release is available on:

Your semantic-release bot 📦🚀

github-actions bot pushed a commit that referenced this issue May 28, 2022
# [1.5.0](v1.4.6...v1.5.0) (2022-05-28)

### Bug Fixes

* [#54](#54) ([c639511](c639511))
* allow absolute paths to tailwind config ([0421a91](0421a91))
* better matching with relative content paths in tailwind.config.js ([f99bc1f](f99bc1f)), closes [#57](#57)
* cssProps working in preview mode ([73cd4b6](73cd4b6))
* **deps:** update docusaurus monorepo to v2.0.0-beta.21 ([a25a8da](a25a8da))
* ensure spreadProps use flat styles on preview ([7c2cc8b](7c2cc8b))
* ensure stroke is set to a valid value ([8970f65](8970f65))
* improve active: styles on web ([30fdfdd](30fdfdd))
* improvements to spreadProps with preview mode ([3d4941a](3d4941a))
* include optional props in useInteraction parsing ([0b6d0a6](0b6d0a6))
* prevent adding empty style arrays to parents ([61780d2](61780d2))
* prevent adding unnecessary event handlers to components ([04ce242](04ce242))
* prevent passing undefined svg props ([244be39](244be39))
* react import for classic JSX ([2e7bf03](2e7bf03))
* remove empty line in generated styles ([20e6973](20e6973))
* rename valueProps to spreadProps. Add cssProps ([3ae8d94](3ae8d94))
* short circuit withStyledChildren when there are no child styles ([8de2e43](8de2e43))
* stop babel appending platform to TailwindProvider ([fc8fdc8](fc8fdc8))
* strokeWidth console warnings on native ([5ace7ff](5ace7ff))
* transform components using fill and stroke ([f4161ef](f4161ef))
* useInteraction not adding handlers ([f3c4127](f3c4127))

### Features

* add parent variant ([a6d8023](a6d8023))
* add preview support for flattened styles ([b5b8273](b5b8273))
* add SVG support ([05897c3](05897c3)), closes [#56](#56)
* allow for styled to parse additional props ([1037027](1037027))
* export new context hooks ([1560afe](1560afe))
@github-actions
Copy link
Contributor

🎉 This issue has been resolved in version 1.5.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant