nx: Unable to determine 'tsconfig.json' file in workspace config.

I have just carried out a migration from 14.2 to latest on an nx angular project and am observing the following:

• my project’s libraries were all generated with the nx-webstorm plugin and are all non-buildable.
• none of the libraries have any reference to a tsconfig.json file in their respective project.json files
• When I run nx migrate --run-migrations some of my libraries get updated but some do not and the logger prints Unable to determine 'tsconfig.json' file in workspace config.
• However when I look at the changes made to the files by the migration, some of the modules that were flagged as skipped have actually been modified

I am at a bit of a loss as to how to get confidence that the migrations have fully run as expected. Any guidance would be much appreciated.

Why is this closed? It doesn’t seem like the issue was ever resolved, based on these last few posts.

@prateek-giddh I can think of two possibilities: 1- one of your projects/libraries doesn’t have the architect properties, even if you don’t need it just add it as empty object "architect": {}, 2- you didn’t specified the builder for your target (the test in your case), for example I use “@nrwl/jest:jest” builder

"test": {
          "builder": "@nrwl/jest:jest",
          "outputs": ["coverage/libs/dir/lib1"],
          "options": {
            "tsConfig": "libs/dir/lib1/tsconfig.lib.json",
            "jestConfig": "libs/dir/lib1/jest.config.js",
            "passWithNoTests": true
          }
        },

@prateek-giddh

"my-lib": {
 ...
  "architect": {
    "build": {
        "options": {
           "tsConfig": "path/to/your/tsconfig.lib.json",
         }
    },
 ...
},

In case the library is not buildable

"my-lib": {
 ...
  "architect": {
    "test": {
        "options": {
           "tsConfig": "path/to/your/tsconfig.lib.json",
         }
    },
  ...
},

@AgentEnder thanks, adding the “tsConfig” to the test target works perfectly.

I think it looks at the test target as well, so you can try adding it there. It’s pretty silly that it’s required at all IMHO, but I know that’s the fix for angular material. I think the main angular packages are similar.

Ok, I figured out that where I have to add that extra tsConfig:

    "build": {
      "executor": "@nrwl/angular:package",
      "outputs": ["dist/libs/core/error"],
      "options": {
=>      "tsConfig": "libs/core/error/tsconfig.lib.json",
        "project": "libs/core/error/ng-package.json"
      },
      "configurations": {
        "production": {
          "tsConfig": "libs/core/error/tsconfig.lib.prod.json"
        },
        "development": {
          "tsConfig": "libs/core/error/tsconfig.lib.json"
        }
      },
      "defaultConfiguration": "production"
    },

Is there an easy way to do it for all the libs in a workspace?

Is there some setting, so that newly generated projects have this already included?

Or is there any other fix I can use?

Thank you!

I only had problems with the migrations of Angular/Material and CDK. The migrations of the main angular packages (core etc.) worked fine.