* Trying out electron 19.0.4
* nvm-for-windows 1.1.7 is busted for node-16.14.2
* Went a bit overboard with the exit I think
* Stepping this back
* Breaking out yarn install
* Print runtime data
* log more data points
* well i'm confused. seeing what happens after these steps
* Lets see if powershell picks up the new PATH
* Maybe shell is refreshed between jobs?
* Installing nvm-1.1.9 manually
* Cleaning up circle.yml and a few other node references.
* Yeah that ain't gonna work
* Trying bash implementation
* Urgh yaml
* Bumping to latest patch version
* Getting a full build + artifacts
* Sourcing node in build step
* More node sourcing
* Run against updated recipes repo
* I'll find all these eventually
* Trigger new build after cache busting
* Let's slim this down to test recipes for a bit
* Good ol' working_directory
* Fixing bad syntax
* Not quite sure where all this is necessary at this point
* Using recipes PR branch
* This isn't necessary here
* Re-enabling jobs
* More node sourcing
* Running kitchensink tests against PR branch
* Moving nvm-windows update to script
* Even more node sourcing
* Removing CI config for merged kitchensink/recipes PRs
* chore: document internal vite options
* try to make pertinant internal dev options more discoverable
* move vite internal references to contributing guide and rebuild references
* fix typo
* Update npm/vite-dev-server/README.md
* add enabling flag for cypress internal vite inspect
* update contributing guide to follow similar wording for internal vite envs
* chore: Updating electron to v18 + node v16.13.2
* Updating origin test, it needs to be fixed a different way
* Removing origin workaround for config_env specs, it should not be necessary.
* Removing now-unused semver dependency
* feat: improved CloudDataSource caching & tests
* feat: pushFragment subscription, for updating the client with remote data (#21408)
* refactor: add pushFragment utility for pushing remote data into the client
* fix: UNIFY-1625 Runs tab not updating in real time (#21412)
* allow returning a Response object in the remoteGraphQLIntercept, handle 401
* removing vite-dev-server local dependency from react-vite-ts-configured system test
* moving some CRA examples over to use the object api for setup
* fixing issue where function API was broken by object API for cy config + devservers
* adding deeply nested react import to project-fixtures for cra
* finishes cutting over cypress/react for sys tests
* chore: adding circle for this feature branch
* chore: moving over many vue + vite system tests to use object API instead of function API (#21080)
* doing webpack-dev-server cutovers
* removing more webpack-dev-server refrences
* fixing snapshots
* bumping yarn.lock
* wip
* fix test
* fix assertion
Co-authored-by: Lachlan Miller <lachlan.miller.1990@outlook.com>
* feat: removing all references for "fresh" dev servers (webpack-dev-server-fresh and vite-dev-server-fresh) (#21094)
Co-authored-by: Lachlan Miller <lachlan.miller.1990@outlook.com>
Co-authored-by: Zachary Williams <ZachJW34@gmail.com>
* chore: add dev-servers as deps to server to be included in the binary (#21091)
* fix bad merge
* fix next types and webpack-dev-server- resolve
Co-authored-by: Lachlan Miller <lachlan.miller.1990@outlook.com>
Co-authored-by: Zachary Williams <ZachJW34@gmail.com>
* Change #__cy_root selector for CT mounting point to be a data-cy-root selector
* moving all of the gets for the container element into the mount-utils
* Force HTMLElement instead of Element
* unskip vue2 tests
Co-authored-by: Lachlan Miller <lachlan.miller.1990@outlook.com>
Co-authored-by: Tim Griesser <tgriesser10@gmail.com>
Rachel