Closed ericaskari closed 2 years ago
Hi, we know that in Nx there will be only one package.json in root and only publishable libraries will have their own package.json after build.
What's the problem with defining those dependencies and devDependencies in root package.json?
can it be somehow configured inside workspace.json or project.json in newer versions?
I personally don't like it because it feels against rules and best practices.
{ "name": "nsapp", "main": "./src/main.ts", "license": "SEE LICENSE IN <your-license-filename>", "version": "0.0.0", "scripts": { "postinstall": "node ./tools/postinstall.js" }, "dependencies": { "@nativescript/core": "*" }, "devDependencies": { "@nativescript/android": "~8.1.1", "@nativescript/ios": "~8.1.0" } }
.
https://github.com/NativeScript/nx#known-issues
Hi, we know that in Nx there will be only one package.json in root and only publishable libraries will have their own package.json after build.
What's the problem with defining those dependencies and devDependencies in root package.json?
can it be somehow configured inside workspace.json or project.json in newer versions?
I personally don't like it because it feels against rules and best practices.
.