-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Type Error when using presetCatppuccin with UnoCSS #107
Comments
|
It seems like it was already fixed with 03d530e, as I have no issues with local source. Will release v1.1.2 soon after bumping dependencies. |
v1.1.3 should be available in npm and JSR soon. Please let me know if it's not fixed or there are other issues. |
Thank you for the update! I've tried v1.1.3, but the issue still seems to persist. |
That seems weird, I can't reproduce it myself. Can you create a simple repository to reproduce, so I can test things? |
It seems to be a version issue in the package.json. The error disappeared when I updated unocss to v0.64.0. |
Ah, that makes sense. This issue (installed UnoCSS and library UnoCSS version not matching) would be warned about with #106 by the package managers itself. |
I am trying to use the
presetCatppuccin
with UnoCSS, but I am encountering the following TypeScript error:Type 'Preset<object>' is not assignable to type 'PresetOrFactory<any> | PresetOrFactory<any>[]'. Type 'Preset<object>' is not assignable to type 'Preset<any>'. Types of property 'rules' are incompatible. Type 'Rule<object>[]' is not assignable to type 'Rule<any>[]'. Type 'Rule<object>' is not assignable to type 'Rule<any>'. Type 'DynamicRule<object>' is not assignable to type 'Rule<any>'. Type '[RegExp, DynamicMatcher<object>, RuleMeta?]' is not assignable to type 'StaticRule'. Type at position 0 in source is not compatible with type at position 0 in target. Type 'RegExp' is not assignable to type 'string'.
This issue started occurring recently after I updated my project, but everything was working fine a year ago when I last used this package. Although the project runs without issues, the TypeScript error is quite annoying.
The text was updated successfully, but these errors were encountered: