* fix(core): perform package.json update if one of the deps is missing
* fix(core): add test for package.json update
Co-authored-by: Juri Strumpflohner <juri.strumpflohner@gmail.com>
BREAKING CHANGES:
The minimal flag is set to true
The syntax flag is set to creators
The useDataPersistence flag is set to false
BEFORE:
By default, the root Store and Effects modules are registered, with a generated feature
By default, the action classes syntax is used for scaffolding
By default, the DataPersistence class in injected and used in Effects
AFTER:
By default, only the root Store and Effects modules are registered
By default, the creator functions are used for scaffolding with schematics
By default, the DataPersistence operators are used in Effects
when determining the package version of dependent libraries, make sure that there's no devDeps or
peerDep already set. In such case don't touch the package.json
This commits adds a proper logic to automatically update the tsconfig paths s.t. they correctly
point to the compiled version of potential other dependent publishable libraries.
Publishable node libraries should use the default npmScope prefix like @proj/mylib. Otherwise it
might lead to inconsistencies when using the library within the monorepo with @proj/mylib and when
publishing it.
* feat(testing): update to jest-preset-angular v8.0.0 part 1
Updates to jest-preset-angular to v8.0.0, includes migrations to fix any existing projects affected
by the jest-preset-angular update.
closes#1979
* feat(testing): update jest-preset-angular to v8.0.0 part 2
Closed issues: #1979, #2165
Co-authored-by: Joshua D. Mentzer <mentzerj@trinity-health.org>
* feat(testing): update jest-preset-angular to v8.0.0 part 3
Co-authored-by: mentzerj <mentzerj@trinity-health.org>
Co-authored-by: Mehrad Rafigh <4339673+mehrad-rafigh@users.noreply.github.com>
* Revert "Revert "fix(core): sort node names for module resolution""
This reverts commit 0b77072fcfe63f8d02fccb73ba138aca99cb7f66.
* fix(core): add target project locator
This will sort nodes by length of the root (high to low) then nodes that have no root.
It also uses TypeScript to first try and resolve a module. If it is not found via TypeScript, it will
fall back to using a string match.
