* Fix some always true/false errors in codebase
Testing out latest TS nightly that can identify when an expression is always true/false. This caught a few likely coding mistakes in our codebase
Unsure about the intent in some of these cases but I've tried my best to understand them. Pinging relevant code owners for the confusing cases
* Bump TS version
* Fix unreachable in build scripts
* Bump versions
* restore intent
* Revert package.json change
* Fixing a few new layer checker errors
These are global in node now
* Skip lib check in integration project
* One more skiplibcheck
* More skip lib
---------
Co-authored-by: Benjamin Pasero <benjamin.pasero@gmail.com>
* playwright - initial version
* browser - use existing page and not create new context
* macOS: document how to remove the security flag
* smoke test - allow to run against server build with --build option
* do not rely on args
* fix path for windows
* smoke test - smoke 💄 and -ci option
Matt Bierner
Martin Aeschlimann
Benjamin Pasero
Jason Ginchereau