* chore(angular): bump ngrx to 13.0.0
* fix(angular): add path filter to resolver for exports
* fix(testing): add mjs to jest module extensions and add dependency on resolve.exports
Co-authored-by: Jason Jean <jasonjean1993@gmail.com>
The scripts property inside project.json is not required. So if it is not provided running the build
command should not fail due to the scripts property being missing.
ISSUES CLOSED: #7178
* docs(angular): update 'npm run' to 'npx nx' for affected commands
The tutorial refers to using 'npm run' for the affected commands, which doesn't work if the
workspace is generated using yarn.
To fix that, change it to 'npx nx' so it works in all cases,
like other places in the docs.
* chore(misc): fix formatting
Co-authored-by: Jason Jean <jasonjean1993@gmail.com>
* feat(storybook): angular v13 and Storybook 6.4 support
* fixup! feat(storybook): angular v13 and Storybook 6.4 support
* fix(angular): add specific storybook prerelease for angular 13 support
* fixup! fix(angular): add specific storybook prerelease for angular 13 support
* fixup! fixup! fix(angular): add specific storybook prerelease for angular 13 support
* feat(angular): add storybook support for angular 13
* fix(angular): temporarily disable storybook tests
Co-authored-by: Colum Ferry <cferry09@gmail.com>
Co-authored-by: Jason Jean <jasonjean1993@gmail.com>
pnpm is deprecating pnpx and suggests using pnpm exec instead.
pnpx still works at the moment, but if for whatever reason it
isn't installed then this pr can make create-nx-worksapce stsill work.
[pnpx documenation](https://pnpm.io/pnpx-cli)
* fix(testing): update tsconfig migration to not warn when no file found
use tsconfig.json references to find what other configs need to be updated. if non when we just exit
* fix(testing): update tests for migration changes
* fix(testing): include any spec. file names in pattern match
accounting for _spec. file names when generating 'test' pattern equivalents
* fix(testing): remove relance on tsconfig.references, walk for all tsconfigs to update
tsconfig.references is not always present. instead visit all files and check if they are tsconfig
json file. if so we update the include/exclude properties where a spec. pattern is found. if the
property isn't set then we do not update it.
* fix(testing): stream line update with devkit
