Daniel 'Eisbehr' Kern

> If you will avoid this issue, I would recommend installing the next tag version, (i.e. vue-i18n v9.3). Currently in beta, this version has not changed much in terms of...

I was able to suppress this warning with a custom typescript definition. Therefore it's not needed to change the package.json in node_modules. Of course, this is not a real fix,...

> A package may be compatible with a large jQuery version range and package.json should only reflect this Yes, exactly this is my problem too! Nice idea.

As far as I undestand his suggestions, thats not the point. Davaid should just look to the `package-lock.json` in a project, if it uses secure deps or not. Because in...

The `package.json` only specifies the versions a module is compatible with. And that can be a very wide range. It has nothing to do with security issues. You have a...

Depends on the module, I think. For some, yes. But for frontend modules, this would not always be an option, imo. Because you wound inject multiple copies of, for example,...

I actually can't, because i'm on holiday now. ;) But some thoughts: - How would you define multiple dynamically then? - Why does `:flat="true"` on Buttons for example works fine?...

> #17211 Oh yes, it seems like the same behavior. But without using volar. 😉

Using webStorm/phpStorm you get volar like errors within the IDE too.

I'm using phpStorm, what should be the same base as webStorm, but I never noticed this. I thought they re-implrmented these checks. I was sure I read about it in...