You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Environment
Provide the content of the package.json file in the project:
Describe the bug
Adding the schematics causes a dependency of @nativescript/schematics in both: dependencies and devDependencies but with different versions.
There should't be a direct dependency but a devDependency with the correct version.
This may be fixed in master, but there isn't a 9.x release on NPM that removes the @angular/http dependency and updates the @nativescript/schematics dependency. Anyone who wishes to create a new shared project has to install the package from the GitHub repository, and even then I was experiencing some issues with the Webpack configuration.
Environment
Provide the content of the
package.json
file in the project:Describe the bug
Adding the schematics causes a dependency of
@nativescript/schematics
in both:dependencies
anddevDependencies
but with different versions.There should't be a direct dependency but a devDependency with the correct version.
This should be respected as well by the migration scripts I think @NathanWalker
To Reproduce
ng add @nativescript/schematics --skipAutoGeneratedComponent
package.json
Expected behavior
The
package.json
should just contain a single devDependency for@nativescript/schematics
within it's version9.x.x
.This can be accomplished by adding the following to the
package.json
since Angular 9.0.0 or greater.Manual injections for the dependency and devDependency should be removed, either
2.0.0
and9.0.0
.The text was updated successfully, but these errors were encountered: