Fix arbitrary length 0 without unit not being recognized
#237
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dcastil
changed the title
0 not being recognized0 without unit not being recognized
size-limit report 📦
|
|
This was addressed in release v1.13.0. |
gjtorikian
added a commit
to gjtorikian/tailwind_merge
that referenced
this pull request
Jun 2, 2023
sebald
referenced
this pull request
in sebald/pattern-analyzer
Jun 19, 2023
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [tailwind-merge](https://togithub.com/dcastil/tailwind-merge) | [`1.12.0` -> `1.13.1`](https://renovatebot.com/diffs/npm/tailwind-merge/1.12.0/1.13.1) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>dcastil/tailwind-merge</summary> ### [`v1.13.1`](https://togithub.com/dcastil/tailwind-merge/releases/tag/v1.13.1) [Compare Source](https://togithub.com/dcastil/tailwind-merge/compare/v1.13.0...v1.13.1) ##### Bug Fixes - Fix `basis-auto` and `basis-full` not being merged correctly by [@​lukasz-kapica](https://togithub.com/lukasz-kapica) in [https:/dcastil/tailwind-merge/pull/242](https://togithub.com/dcastil/tailwind-merge/pull/242) **Full Changelog**: dcastil/tailwind-merge@v1.13.0...v1.13.1 ### [`v1.13.0`](https://togithub.com/dcastil/tailwind-merge/releases/tag/v1.13.0) [Compare Source](https://togithub.com/dcastil/tailwind-merge/compare/v1.12.0...v1.13.0) This release focuses on improvements to the docs. ##### New Features - Add intro video from Simon Vrachliotis to docs by [@​dcastil](https://togithub.com/dcastil) in [https:/dcastil/tailwind-merge/pull/239](https://togithub.com/dcastil/tailwind-merge/pull/239) - [@​simonswiss](https://togithub.com/simonswiss) made an intro video to tailwind-merge which I added to the docs. Check it out [here](https://togithub.com/dcastil/tailwind-merge/blob/v1.13.0/docs/what-is-it-for.md#video-introduction)! - Add docs about when to use tailwind-merge by [@​dcastil](https://togithub.com/dcastil) in [https:/dcastil/tailwind-merge/pull/230](https://togithub.com/dcastil/tailwind-merge/pull/230) - I added a new page to the docs about [when and how to use tailwind-merge](https://togithub.com/dcastil/tailwind-merge/blob/v1.13.0/docs/when-and-how-to-use-it.md) which should help you to decide whether you should use it and what alternative approaches exist. - Make it clearer in docs that tailwind-merge supports composition of class strings by [@​dcastil](https://togithub.com/dcastil) in [https:/dcastil/tailwind-merge/pull/229](https://togithub.com/dcastil/tailwind-merge/pull/229) - Add npm package provenance by [@​dcastil](https://togithub.com/dcastil) in [https:/dcastil/tailwind-merge/pull/219](https://togithub.com/dcastil/tailwind-merge/pull/219) - GitHub introduced a new security feature to verify which source commit and build file were used for a specific npm package version. tailwind-merge now publishes provenance signatures alongside all releases on npm. [Read more on the GitHub blog.](https://github.blog/2023-04-19-introducing-npm-package-provenance/) ##### Bug Fixes - Fix arbitrary length `0` without unit not being recognized by [@​dcastil](https://togithub.com/dcastil) in [https:/dcastil/tailwind-merge/pull/237](https://togithub.com/dcastil/tailwind-merge/pull/237) - Fix typo in comment in default-config.ts by [@​CrutchTheClutch](https://togithub.com/CrutchTheClutch) in [https:/dcastil/tailwind-merge/pull/227](https://togithub.com/dcastil/tailwind-merge/pull/227) **Full Changelog**: dcastil/tailwind-merge@v1.12.0...v1.13.0 </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://app.renovatebot.com/dashboard#github/sebald/pattern-analyzer). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNS4xMTAuMCIsInVwZGF0ZWRJblZlciI6IjM1LjExMC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
1 task
](https://renovatebot.com){kind=link}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #234