disable name mangling when building for production with optimization on,
in order not to break
features relying on runtime reflection
ISSUES CLOSED: #8537
* 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.
node:build currently has tsPlugins options to invoke TypeScript Plugins (transformers). This PR
brings the same functionality to node:package
ISSUES CLOSED: #7420
* 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
* fix(node): prevent extra kebab-case files being generated when pascal case option is on
* fix(node): remove unused variable
Co-authored-by: Jason Jean <jasonjean1993@gmail.com>
* fix(node): bundle new expectations into the existing test cases
Co-authored-by: Samdanae Imran <samdanae.imranuzzaman@serko.com>
Co-authored-by: Jason Jean <jasonjean1993@gmail.com>
* feat(node): add TS plugins support for build executor
ISSUES CLOSED: #2147
* docs(node): add tsPlugins to node build executor schema
* chore(node): reformat schema json
* chore(repo): update yarn.lock
* cleanup(node): adjust tsPlugins test for node build executor
* cleanup(node): remove packageJson check for tsPlugins test
* cleanup(node): increase timeout for tsPlugins e2e test
* cleanup(node): use type import for typescript types instead of importing typescript
Co-authored-by: Chau Tran <ctran@Chaus-MacBook-Pro.local>
Co-authored-by: Miroslav Jonas <missing.manual@gmail.com>
* cleanup(core): remove last references to local appRootPath
* chore(core): add deprecation comment to appRootPath
* chore(node): fix failing test due to typescript change
