Closed minijus closed 2 years ago
@qortex can you try deleting node_modules and package-lock.json and do npm install and then check?
Just tried it, still got the warning.
@qortex that would be a valid warning, you must have a property called configurations in some project configuration somewhere or as a root property in workspace json or nx.json.... It may be a bit hard to locate the property if you have several projects, but it is a misconfiguration since that doesn't do anything and you'd probably expect it to.
@qortex that would be a valid warning, you must have a property called configurations in some project configuration somewhere or as a root property in workspace json or nx.json.... It may be a bit hard to locate the property if you have several projects, but it is a misconfiguration since that doesn't do anything and you'd probably expect it to.
Ok thanks for the help, I'll look for it then!
Hey, I just updated to the newest version of nx (14.5.6) and I'm getting a lot of warnings like before
This whole thing seems to be totally random. I updated our project to 14.5.6 two days ago and all warnings disappeared in the process
Before I tried to remove node_modules, yarn.lock. But it doesn't work for me
What interesting, that I tried to setup another project and there it works properly
have you updated manually to 14.5.6 or via migrate? @B1Z1
Via migrate
This fixed the problem for me after migration: in file decorate-angular-cli.js change the require('@nrwl/cli/lib/decorate-cli').decorateCli(); to: require('nx/src/adapter/decorate-cli').decorateCli();
@maphe @bjornharvold I also had the issue with "Path "/tsconfig.json" does not exist.". The cause was that my tsconfig in root dir had custom name tsconfig.base.json. Workaround is to temporary rename this file to tsconfig.json, run that single migration (by manual modifying migrations.json to contain only that single migration) and changing name back to original.
Apart of that I also report multiple warnings "Project extension with invalid name XXXXX found."
I'm having a similar issue " Unable to determine 'tsconfig.json' file in workspace config". When renaming tsconfig.base.json, did you have to do more than just rename the file? ie, did you have to update all the apps and libs tsconfig.json to point to the newly renamed base?
Hello there, still have
with nx 14.5.10
probably an issue with schema in angular.json ? seems like it's saying that's my schema / tags and prefix for my angular libs are not well recognized.
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.
Current Behavior
Building Angular application produces many warning:
The warning is thrown from: https://github.com/angular/angular-cli/blob/main/packages/angular_devkit/core/src/workspace/json/reader.ts#L205
name
is not logged when running Angular builder fromnx
cli. However, when debugging names that produce warnings are$schema
,configFilePath
,tags
.Expected Behavior
There should be no such warnings.
Steps to Reproduce
Build Angular application with latest version on nrwl/nx and Angular (v14.0.6).
Environment