Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 8 commits
- 5 files changed
- 4 contributors
Commits on Jan 18, 2023
-
chore: add Tailwind readme section (#65)
* Add usage with Tailwind documentation Add documentation on how to enable Tailwind IntelliSense inside `clsx` functions Fixes #64 * Update readme.md Co-authored-by: Luke Edwards <luke.edwards05@gmail.com> * Update readme.md Co-authored-by: Luke Edwards <luke.edwards05@gmail.com>
Commits on Feb 28, 2023
Commits on Jul 15, 2023
-
break: include "exports" map w/ "types" conditions (#57)
The non-standard `package.json` field `module` was used. This pointed to a faux ESM file (Uses ESM syntax, but has a `.js` file extension in a package which doesn’t specify `"type": "module"`. ESM support was fixed by using the `.mjs` file extension for the ESM export and defining a proper `exports` field in `package.json. The types reflected a package that has the `module.exports.default` field. This was incorrect. The CommonJS types have now been fixed to use `export =`, which is the correct way to type modules that use `module.exports` assignments. Additional types were added for ESM support.
-
-
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.2.1...v2.0.0