Open tryforceful opened 1 year ago
This has been slowly getting ππΌs and it's been a month, any update?
π¬π¬π¬
Any updates here? Thanks
For those who's waiting for this fix, for time being you can bypass this with explicit deps overriding.
With yarn:
"resolutions": {
"meow": "^9.0.0"
}
With npm it's overrides
.
Any updates? Stylelint 16 is using meow
^13.0.0
. Pinning meow
to version 9 is not a permanent solution.
same issue,how to resolve
same issue,how to resolve?
Describe the bug
The latest Stylelint v15.10.1 now uses
meow@^10
, updating to that version to remove a recently announcedsemver
vulnerability from the dependency tree.However, using
meow@10
with the latestvite-plugin-checker
generates errors for me when trying to build with Vite:It seems likely to me that the reason is because the breaking changes to
meow@10
are that the package is fully ESM now: https://github.com/sindresorhus/meow/releases/tag/v10.0.0Using
meow@9
doesn't generate this error for me.Reproduction
See minimal repro at this repo: https://github.com/tryforceful/poc--20230714-meow-vite-plugin-checker
Try to build that package with
pnpm i; pnpm dev
and it will generate the above error.If you comment out these lines in the
vite.config.js
which enable vite-plugin-checker:the error also goes away, showing that vite-plugin-checker is having difficulty using the implicit dependency
meow@10
from stylelint.Note that running
stylelint
alone in this repo also works fine.Expected behavior
I expect no error when running
pnpm dev
while using the latestvite-plugin-checker
andstylelint
(v15.10.1)System Info
Additional context
See #255 where upgrading
meow
is also being requestedValidations