Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Command failing after `nx migrate latest`

See original GitHub issue

After migrating to the latest version of the NX suite, if I try to run nx run workspace:version I get this error:

"BuilderInputSchema" schema is using the keyword "id" which its support is deprecated. Use "$id" for schema ID.
"BuilderOutputSchema" schema is using the keyword "id" which its support is deprecated. Use "$id" for schema ID.
schema with key or id "http://json-schema.org/draft-07/schema" already exists

@jscutlery/semver version is 2.1.0.

Any idea about how to solve this?

Issue Analytics

State:
Created 2 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

2reactions

mtrefzercommented, May 17, 2021

Perfect now everything is back to normal and thank you for your amazing work @edbzn

2reactions

edbzncommented, May 16, 2021

Hi @LuckeeDev, this problem was resolved in version 2.2.0, thanks for reporting!

Top Results From Across the Web

nx migrate latest fail · Issue #6214 · nrwl/nx - GitHub

Current Behavior When I run nx migrate latest I get: Fetching meta data about packages. It may take a few minutes.

How to use nx migrate latest command? - Stack Overflow

I try to migrate from angular 11 to angular 12 using the nx migrate command, but I've an error I can't understand what...

Advanced Update Nx

When you run into problems running the nx migrate --run-migrations command, here are some solutions to break the process down into manageable steps....

nx cannot read properties of undefined (reading 'endswith')

Create a project using nx 14.0.2, migrate to 14.1.4 and try to run a nx command. Failure Logs. npm ERR! path /home/circleci/project ...

Nx/community - nrwl - Gitter

Command failed with exit code 1: npm run --silent build-storybook ... @cuznerdexter Since that time I didn't create a new workspace with a...