* fix(android): nested frames were sometimes not recreated (#9748)
Co-authored-by: Eduardo Speroni <edusperoni@gmail.com>
* feat: testID property for use with e2e testing without interfering with a11y
* feat: better testID support along a11y
wip
* fix: make sure we have a defined id
* feat: --env.e2e to enable testID
* chore: return if using testID
* chore: cleanup
Co-authored-by: Eduardo Speroni <edusperoni@gmail.com>
Co-authored-by: Igor Randjelovic <rigor789@gmail.com>
* fix(webpack): respect hmr flag
* fix(webpack): ensure correct loader order is used
* chore: cleanup
Co-authored-by: Igor Randjelovic <rigor789@gmail.com>
* fix(webpack): Fail build in case of compilation errors.
WebPack's own documentation states that the `err` object **will not**
include compilation errors.
https://webpack.js.org/api/node/#webpack
This fix addresses compilation errors by setting the correct `process.exitCode`
looking at the result of the `stats.hasErrors()` call.
* fix(tsc): Ensure that TypeScript compilation errors are handled.
The `async` flag of the `fork-ts-checker-webpack-plugin` will (by default
in development mode) avoid reporting any errors detected by `tsc` back
to webpack:
https://github.com/TypeStrong/fork-ts-checker-webpack-plugin#options
> If `true` reports issues **after** webpack's compilation is done.
> Thanks to that it doesn't block the compilation.
The problem in this case is that any compilation error will be then
undetectable by the `WatchStatePlugin` which will happily tell the
NativeScript CLI to continue with the build process.
* fix(cli): Do not send the `compilation` message to the CLI on errors.
When the compilation fails, this patch will prevent for the `compilation`
message to be sent back to the CLI, preventing broken builds hitting the device.
* feat: file replacement handling for TS and pure file copy replacements
* test: add tests for replacements & refactor a bit
Co-authored-by: Igor Randjelovic <rigor789@gmail.com>
