* chore(angular): support angular 13
Support Angular 13
chore(angular): support ng 13 next 11
chore(angular): upgrade tslib dep
chore(angular): update package and ng-packagr-lite executors to align with ng-packagr v13
chore(angular): update test snapshots with ts version
fix(angular): buildable lib tsconfig transform test
* chore(angular): sync ng-packagr changes to the package and ng-packagr-lite executors
* chore(angular): add migrations
* chore(angular): rxjs7
* feat(angular): check rxjs version to install
* feat(angular): update jest resolver to resolve esm
* chore(angular): fix version
* chore(angular): support jest-preset-angular
* fix(angular): tests
* fix(angular): fix e2e tests and add .angular to gitignore
* fix(angular): fix jest transformers ignore pattern
* fix(angular): fix node test
* fix(angular): fix workspace test
* fix(angular): import marble utils from jasmine-marbles instead of @nrwl/angular/testing
* feat(angular): update ngrx to 13.0.0-beta.;0
* fix(angular): temporarily skip test with pnpm
* fix(angular): bump jest-preset-angular to fix jest performance issues
* fix(angular): webpack-browser and server schema changes
Co-authored-by: Leosvel Pérez Espinosa <leosvel.perez.espinosa@gmail.com>
Co-authored-by: Jason Jean <jasonjean1993@gmail.com>
* fix(testing): add .test. files to spec tsconfig template
add support for .test.ts and with supportTsx .test.{js|tsx|jsx} files
in the tsconfig.spec.json template.
Note each package that excludes testing files will need to be updated to
exclude the new files (coming in future commits)
* fix(angular): add .test.ts support in tsconfigs
add .test.ts in angular jest template
update angular generators to exclude test files
* fix(gatsby): add .test. file prefixes to tsconfig ignore
ignore the new .test.{js|ts|jsx|tsx} files added to jest configs
* fix(react): add .test. file prefix to app/lib tsconfigs
add .test.{ts|js|tsx|jsx} files to be excluded by app/lib tsconfig
* fix(node): add .test. file prefix to app/lib tsconfig
add .test.{ts|js|tsx|jsx} files to be excluded by app/lib tsconfig
ISSUES CLOSED: #7263
* fix(nest): update tests for new .test.ts files in tsconfig
update tests to account for changes in node generators which add .test.ts to the exclude of
tsconfigs
* fix(express): update tests to account for new tsconfig changes
updated snapshots
added new patterns for tsconfig
* fix(linter): update snapshots for new tsconfig changes
snapshot updated to include new .test.ts file changes for tsconfig
* fix(node): update testing to account for spec tsconfig changes
add .test.ts files in e2e tests
* fix(testing): add migration for tsconfig changes
initial migration and test for tsconfig changes
* chore(testing): add to migrations collection
add the update-ts-config-for-test-filenames to migrations
* fix(testing): fix filesystem issue with jest tests
mock readConfig to always return an basic config to prevent issues of not finding a config in non
linux environments, aka missing /root
* cleanup(testing): update error message
update message logged when tsconfig isn't found to mention what was trying to be accompished so it
can be manually updated if desired.
* feat(core): standalone project configuration is default
* chore(core): changes to e2e tests
* fix(core): intuit projects when inside their directories when using project.json files
* chore(core): e2e changes
* fix(core): standalone configurations work with npm-project generator
* chore(core): e2e tests should use standalone configurations
* chore(core): e2e fixes per review
* chore(core): fix some broken tests
* docs(core): update docs to represent master -> main
* chore(core): review changes
Co-authored-by: Jason Jean <jasonjean1993@gmail.com>
* chore(core): add migration script for backwards-compat w/ main default.
Co-authored-by: Jason Jean <jasonjean1993@gmail.com>
Currently, we split on path.sep in normalizePath. This results in differing results based on if the host file system is unix or windows. I
would expect that normalizePath(...) should return the same result wether or not it was executed in windows.
devkit's generateFiles function excludes parsing binary files with the templating engine.
This
patch adds .tgz files to the list of binary files to ignore.
* feat(devkit): make nx.json optional (#5678)
Allow project configuration functions to work without nx.json configuration file, this is particulary handy for regular Angular CLI projects.
* docs(devkit): make `NxJsonConfiguration` partial
Co-authored-by: Jason Jean <jasonjean1993@gmail.com>
Add font file extensions to the list of extensions that should not be rendered with ejs
ISSUES CLOSED: #5213
Co-authored-by: egiroux <erika.giroux@ubisoft.com>
* fix(core): wrapped angular schematics should be able to update newly created standalone projects
Wrapped angular schematics inside of generators should be able to update a newly created standalone
project configuration
ISSUES CLOSED: #6342
* fix(core): angular devkit schematics should normalize project paths before writing
Wrapped angular schematics inside of generators should be able to update a newly created
standalone
project configuration
ISSUES CLOSED: #6342
ISSUES CLOSED: #6353
* fix(core): wrapped angular-devkit schematics should pick up standaloneAsDefault
ISSUES CLOSED: #6354
* fix(devkit): removeProjectConfiguration should remove path for project.json from workspace.json
When using standalone config files, removing a project's config should also remove its entry in the
workspace file.
* fix(misc): @nrwl/workspace:rm should work with standalone config files
When using standalone config files, removing a project's config should also remove its entry in
the
workspace file.
