Error: > NX Cannot update Project header at packages/header. It doesn't exist or uses package.json configuration.

[MuthupandiG]

Hi Team,
I have upgraded my monorepo from Lerna (v3) to Nx (v15) and I m using workspaces config in package.json for dependency installation instead of lerna bootstrap and the Node Env is v16.5 However, I am getting below error when running

nx g @jscutlery/semver:install

package.json config:

"workspaces": [
"packages/**"
]

Selected Options:

NX Generating @jscutlery/semver:ng-add

✔ Lock/sync versions between packages? (y/N) · false
✔ Enforce conventional commits? (Y/n) · true
? Which projects would you like to version independently? Selected Header project

And, the error is:

NX Cannot update Project header at packages/header. It doesn't exist or uses package.json configuration.

[MuthupandiG]

Verbose error:

Cannot update Project header at packages/header. It doesn't exist or uses package.json configuration.
at validateProjectConfigurationOperationsWithoutWorkspaceJson (/Users/xxxx/Documents/Lerna_Nx/projectA/node_modules/@jscutlery/semver/node_modules/@nrwl/devkit/src/generators/project-configuration.js:355:15)

[herrlegno]

I'm getting the same error with a fresh install with nx:

[edbzn]

@herrlegno could you provide the output of nx report please?

[herrlegno]

@herrlegno can you provide the output of nx report please?

[herrlegno]

@edbzn is there a way to migrate from package.json to project.json that seems to be the way to be able to use this versioning plugin?

[herrlegno]

@edbzn I found a workaround to make it work. Just add a project.json file with:

{
  "name": <project name>,
  "targets":{}
}

before running

ng g @jscutlery/semver:install

It will add the nx runners to it, and if you run:

nx affected --target version [...options]

after the commits it will run as expected.

For reference after doing what I described in one of my packages I this project.json:

{
  "name": "eslint-config",
  "$schema": "../../node_modules/nx/schemas/project-schema.json",
  "targets": {
    "version": {
      "executor": "@jscutlery/semver:version",
      "options": {
        "preset": "conventional"
      }
    }
  }
}

[herrlegno]

@edbzn Today I wanted to update a package but it's not working again:

It doesn't detect the changes

[edbzn]

@herrlegno does it work when using run-many command?

nx run-many --target version 

[herrlegno]

Kinda works but It creates also versions for packages that are not modified. Also git is executed in parallel and it doesn't like to do that:

[edbzn]

Yeah, you have to explicitly give --parallel=1 for the concurrent Git access, anyway run-many is not what you need. I checked and it seems that actually, our executor is not compatible with package.json based projects. This is something we need to consider in #655, but for now, you need to use a project.json file to be able to configure executors.

[herrlegno]

@edbzn Today I wanted to update a package but it's not working again:

It doesn't detect the changes

@edbzn sorry for bothering you again. I found out the problem that i mentioned was because i was running affected version with main as base branch and the commits were on main so there was no change. After changing the base branch to origin/main it runs perfectly.

Running this (in my example) works as expected:

nx affected --target version --base=origin/main --parallel=1

Sorry for all the trouble, first time using Nx + Automatic versioning.

[edbzn]

No problem! Happy it works for you.