Update from 2.4.0 to 3.1.5 cause type incompatibility

[emcdaniel-sungage]

We're trying to update to remediate these vulnerabilities:

• SNYK-JS-ESCAPETECHGRAPHQLARMOR-10043599
• SNYK-JS-ESCAPETECHGRAPHQLARMORCOSTLIMIT-10043598

But when we do so we get the following error when compiling the TypeScript

error TS2322: Type 'import("/node_modules/@escape.tech/graphql-armor-cost-limit/node_modules/graphql/validation/ValidationContext").ValidationRule[]' is not assignable to type 'import("/node_modules/graphql/validation/ValidationContext").ValidationRule[]'.
  Type 'import("/node_modules/@escape.tech/graphql-armor-cost-limit/node_modules/graphql/validation/ValidationContext").ValidationRule' is not assignable to type 'import("/node_modules/graphql/validation/ValidationContext").ValidationRule'.
    Types of parameters 'context' and 'context' are incompatible.
      Type 'import("/node_modules/graphql/validation/ValidationContext").ValidationContext' is not assignable to type 'import("/node_modules/@escape.tech/graphql-armor-cost-limit/node_modules/graphql/validation/ValidationContext").ValidationContext'.
        Types have separate declarations of a private property '_schema'.

validationRules: apolloProtection.validationRules,

From this line of code
validationRules: apolloProtection.validationRules (in a Nest.js codebase if that matters).

[mrs-eload]

We have the exact same typing issue after Snyk update.
We managed to ignore it by ts-ignore validationRules in appolo configuration object but it still fails when instantiating ApolloArmor

{
  // @ts-ignore
  validationRules: apolloArmor.validationRules
}

[thibaudlabat]

Could you provide a minimal code example to reproduce the issue? Or at least your package versions?

[emcdaniel-sungage]

Could you provide a minimal code example to reproduce the issue? Or at least your package versions?

Sorry, which packages do you mean? (as in the issue title) we were on 2.4.0 and saw the error when moving to 3.1.5. Did you want our full package.json?

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[arvindell]

I have this same issue

[M0ngi]

Could you provide a minimal code example to reproduce the issue? Or at least your package versions?

Sorry, which packages do you mean? (as in the issue title) we were on 2.4.0 and saw the error when moving to 3.1.5. Did you want our full package.json?

@emcdaniel-sungage A minimal reproduction repo for us to reproduce the issue, with package.json showing GraphQL Armor version & graphql version you are using.