fix(misc): skip projects configured in package.json for adding schemas

[FrozenPandaz]

Current Behavior

Having projects configured with something that is not project.json will cause the migration to fail.

Expected Behavior

Projects configured with something that is not project.json will be skipped during the migration.

Related Issue(s)

Fixes #

[nx-cloud-staging]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 7dbc63e. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 12 targets

• nx affected --target=e2e --base=ef5334bc3cdd5edf30671f4d8953a31b0560549a --head=7dbc63eafcc1c8b4f38b22722eb6591ade572165 --exclude=e2e-storybook,e2e-storybook-angular,e2e-react-native,e2e-detox,e2e-make-angular-cli-faster --parallel=1
• nx affected --target=test --base=ef5334bc3cdd5edf30671f4d8953a31b0560549a --head=7dbc63eafcc1c8b4f38b22722eb6591ade572165 --parallel=1
• nx affected --target=build --base=ef5334bc3cdd5edf30671f4d8953a31b0560549a --head=7dbc63eafcc1c8b4f38b22722eb6591ade572165 --parallel=3
• nx-cloud record -- yarn depcheck
• nx affected --target=lint --base=ef5334bc3cdd5edf30671f4d8953a31b0560549a --head=7dbc63eafcc1c8b4f38b22722eb6591ade572165 --parallel=3
• nx-cloud record -- yarn nx workspace-lint
• nx-cloud record -- yarn check-lock-files
• nx-cloud record -- yarn check-commit
• nx-cloud record -- yarn nx format:check --base=ef5334bc3cdd5edf30671f4d8953a31b0560549a --head=7dbc63eafcc1c8b4f38b22722eb6591ade572165
• nx-cloud record -- yarn check-imports
• nx-cloud record -- yarn documentation
• nx build typedoc-theme

---

Sent with 💌 from NxCloud.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
nx-dev	✅ Ready (Inspect)	Visit Preview	Aug 26, 2022 at 7:08PM (UTC)

[rhermes62]

Edit: Its actually a lerna issue, see here for more details. Please ignore original comment

> Having projects configured with something that is not project.json will cause the migration to fail.

@FrozenPandaz do you have more details on what migration was failing that necessitated this change?

I think this change ended up causing the issue reported here.

Lerna documentation recommends nx configurations in package.json which I think this broke:

* https://lerna.js.org/docs/concepts/how-caching-works#what-is-cached
* https://lerna.js.org/docs/api-reference/configuration#project-specific-configuration

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.