* feat(js): implement a smarter compiler (tsc, swc) helper dependency detection
ISSUES CLOSED: #10270
* chore(js): add test to check for swc/helpers upon build lib
* fix(testing): jest.preset.ts => jest.preset.js
* fix(testing): update to export default
* fix(testing): migration for moving to export default
* fix(testing): add eslint ignore comments for jest config properties
fixes: #10021
* fix(testing): update tsconfig.spec.json for next apps with project parserOptions
fixes: #9982
* fix(testing): prevent renaming root jest preset
fixes: #9973
* fix(testing): update snapshots for export default
* fix(testing): bump migration version to run
* fix(testing): make sure default jest tests pass for various projects
* fix(js): generate correct jest config for --compiler=swc --js
* fix(js): fix(js): adding missing babelrc for tsc compiled libraries
ISSUES CLOSED: #8600, #8793
ISSUES CLOSED: #8600, #8793
* feat(js): adds the --skipBabelConfig flag to prevent .babelrc file generation
ISSUES CLOSED: #8600, #8793
ISSUES CLOSED: #8600, #8793
* feat(js): adds the --includeBabelRc flag to the library generator
adds the --includeBabelRc flag to the library generator, and a mechanism to automatically detect the
nrwl/web plugin, which requires auto-generation of the babelrc even when not explicitly set by the
user
ISSUES CLOSED: #8600, #8793
* feat(testing): move jest config to .ts
move jest config and preset to ts files
ISSUES CLOSED: #8344
* fix(testing): update tests for jest.config.ts changes
update tests broken by renaming jest fils to ts files
* docs(testing): add example on how to use ts path aliases within jest global setup/teardown
Jest global setup/teardown scripts run before path aliaes are mapped, so the path resigstration must
happen in the userland global scripts that are set to run
initially the thought of doing this within
the jest executor was thought, but this will provide an inconsistent way to running tests if the
tests are run via an editor plugin or calling `jest` directly; therefore, it's deferred to register
the paths within userland files that are needing the paths to be registered in order to allow for
proper handling (cleanup) and not to overcall unneeded features when global scripts are not in use
for those not using the feature.
ISSUES CLOSED: #8709
* cleanup(testing): test the usage of jest global scripts to ensure no regressions
streamline e2e jest project testing and update global tests to test global functions are working as
intended
