Schema validation warnings when running nx lint

[mcmxcdev]

We just upgraded all nx-related libraries from 14.5.4 to 14.5.8 and encountered an issue with nx lint commands.

Current Behavior

There are various lines which look related to schema validation:

> nx run shared-utils:lint

Linting "shared-utils"...
can't resolve reference #/definitions/directiveConfigSchema from id #
can't resolve reference #/definitions/directiveConfigSchema from id #
can't resolve reference #/definitions/directiveConfigSchema from id #
can't resolve reference #/definitions/directiveConfigSchema from id #

Expected Behavior

No lint warnings

Steps to Reproduce

I was able to pinpoint it to extending the following nx plugin:

{
  "files": ["*.ts", "*.tsx"],
  "extends": ["plugin:@nrwl/nx/typescript"],
}

Removing this configuration removes the warnings.

Environment

   Node : 16.16.0
   OS   : linux x64
   pnpm : 7.9.4
   
   nx : 14.5.8
   @nrwl/angular : Not Found
   @nrwl/cypress : 14.5.8
   @nrwl/detox : Not Found
   @nrwl/devkit : 14.5.8
   @nrwl/eslint-plugin-nx : 14.5.8
   @nrwl/express : Not Found
   @nrwl/jest : 14.5.8
   @nrwl/js : 14.5.8
   @nrwl/linter : 14.5.8
   @nrwl/nest : 14.5.8
   @nrwl/next : 14.5.8
   @nrwl/node : 14.5.8
   @nrwl/nx-cloud : 14.4.1
   @nrwl/nx-plugin : Not Found
   @nrwl/react : 14.5.8
   @nrwl/react-native : Not Found
   @nrwl/schematics : Not Found
   @nrwl/storybook : 14.5.8
   @nrwl/web : 14.5.8
   @nrwl/workspace : 14.5.8
   typescript : 4.7.4
   ---------------------------------------
   Local workspace plugins:
   ---------------------------------------
   Community plugins:

[meeroslav]

Thank you @mcmxcdev for reporting this issue.

I was, unfortunately, unable to reproduce it. Can you perhaps provide a minimal repo where this is reproducible?
Additionally, can you try migrating to the latest version and see if it's still happening on your monorepo?

[mcmxcdev]

Hey Miroslav, this was actually coming from typescript-eslint/typescript-eslint#5525 and has been fixed in the mean time. Sorry for keeping this open.

[github-actions]

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.