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

chore: indicate compatibility with new v4 major #203

Merged
merged 1 commit into from
Jun 28, 2024

Conversation

danielroe
Copy link
Contributor

With Nuxt 4 on the horizon, this updates the module compatibility definition to allow it to be installed on Nuxt v4. (Otherwise Nuxt will indicate the module might not be compatible.)

When Nuxt v4 comes out then you might decide or need to make breaking changes in this module and release a new major, but hopefully the migration should be smoother. 🙏

👉 You can follow this and other changes in nuxt/nuxt#27613 - please feel free to provide feedback as well!

@halilyuce
Copy link

@danielroe Will there also be an update for vulnerability issues? npm audit constantly gives errors due to 3 high risks in this package.

@danielroe
Copy link
Contributor Author

I'm not a maintainer of this package.

@harlan-zw harlan-zw merged commit f20e0e1 into windicss:main Jun 28, 2024
1 check passed
@harlan-zw
Copy link
Member

@danielroe Will there also be an update for vulnerability issues? npm audit constantly gives errors due to 3 high risks in this package.

afaik there is one related to fast-glob dependency tree which should fix itself mrmlnc/fast-glob#444, what others are you getting?

@halilyuce
Copy link

@danielroe Will there also be an update for vulnerability issues? npm audit constantly gives errors due to 3 high risks in this package.

afaik there is one related to fast-glob dependency tree which should fix itself mrmlnc/fast-glob#444, what others are you getting?

#202

@halilyuce
Copy link

halilyuce commented Jul 2, 2024

@harlan-zw It seems to be caused by the lodash package.
image

@harlan-zw
Copy link
Member

You should use the latest version

@halilyuce
Copy link

halilyuce commented Jul 3, 2024

You should use the latest version

Thanks, I tried updating to the latest version (3.0.0) but got an error saying this version was not available and when I ran npm upgrade I saw it was 3.0.1 lol

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.

3 participants