Inflight is reported as vulnerability in type-graphql about type-graphql HOT 4 CLOSED

That's why I say, if you don't use resolvers: ["./**/*.ts"] glob string path, then the glob package is not called in real time, so it's not making any vunerability.

I don't have any plans for bumping deps of old versions. So either use npm audit fix or yarn resolutions solutions or upgrade to v2.0.0-beta.2 😉

Thanks for your response. Issue resolved.

from type-graphql.

By npm audit fix? Yarn resolutions?
If you do not use glob paths string for resolvers, the glob package is not used.

from type-graphql.

By npm audit fix? Yarn resolutions? If you do not use glob paths string for resolvers, the glob package is not used.

I listed this tree structure by used the cmd npm list --depth=3, from this result you can able to see the glob deps used by the package type-graphql

from type-graphql.

That's why I say, if you don't use resolvers: ["./**/*.ts"] glob string path, then the glob package is not called in real time, so it's not making any vunerability.

I don't have any plans for bumping deps of old versions.
So either use npm audit fix or yarn resolutions solutions or upgrade to v2.0.0-beta.2 😉

from type-graphql.