* web - first cut `yarn web` via our server
* properly pipe output
* web - remove traces of web playground
* web - remember last opened workspace for convinience
* use vscode-test-web for server less, clean up web commands
* fix comment
* fix `yarn web`
* rename to code-server
* open system browser
* code-server script: use minimist
* test resolver: use ./scripts/code-server
* integartion tests: fix code-server command name
Co-authored-by: Martin Aeschlimann <martinae@microsoft.com>
* Revert service worker usage of MessageChannel
Reverts 66b6adf035
While I'm not 100% about this, I think 66b6adf035 causes resourses to occasionally not load. I believe this can happen if the service worker is unitilized while the webview remains active. I can't reproduce this myself so it may be related to memory pressure or resource usage, however relying on the service worker not being reinitilized does seem like a potentially bad idea https://stackoverflow.com/questions/34775105/what-causes-the-global-context-of-a-service-worker-to-be-reset
Will investigate if there's another way to achive this since using MessagePort did clean up the code and slightly improve performance
* Bump webview commit versions
* smoke - make sure app is closed when `app.start` fails
* smoke - `capturePage` to fallback to active window
* smoke - more logging around remote resolving
Improvements came from waiting for search to complete before clicking buttons, clearing previous results before starting the search, and adding a retry around the clicking.
* smoke - record traces per test and not entire suite
* smoke - only persist failing tests
* smoke - cleanup
* smoke - more logging
* smoke - push a test failure to proof the point
* smoke - switch back to chrome for smoke tests
* smoke - warn when exit takes 10s
* Revert "smoke - push a test failure to proof the point"
This reverts commit e572a0c40d.
