* docs: add more details to the @packages/example deploy process
* Update guides/release-process.md
Co-authored-by: Jennifer Shehane <jennifer@cypress.io>
---------
Co-authored-by: Jennifer Shehane <jennifer@cypress.io>
* update example build scripts
* remove old scaffolding relics
* update
* Fix some issues with scaffolding
* Correctly fix issues with scaffolding
* Replace old onboarding with new banner
* Add ability to remove scaffolded files
* Add banner for new users
* Update tests for new scaffolding
* Compare file sizes before removing
* Add tests for remove file
* Save when user opened cypress rather than boolean
* Update intro link and add tets for banners
* fix small issue
* Update design and copy of onboarding banners
* Update style of new spec file button
* Improve outline button active statE
* Update design of new project a bit more
* Fix specs list tests
* Update banner copy and layout
* Update banner copy and layout
* Switch to docs style alerts
* Fix testing logic
* Update banner styles a bit
* Update banners
* Add confirmation modal for delete specs
* Update tests and fix states
* Upgrade kitchensink dep
* Upgrade kitchen sink version and fix unit tests
* Update integration scaffolding test
* Add further description to warning modal
* Update test for new user and new project case
* Remove check to file tree when removing files
* Update kitchensink version
* Fix edge case where banner could appear when no files have been scaffolded
* Fix tests
* Update styling for 'note' when deleting files
* fix issue with path on windows
* Change remove command
* Fix rm dir
* Fix for windows
* Try to use appveyor to test
* appveyor please
* getting some feedback
* Why doesn't this work
* more info
* I have a feeling this works
* maybe its the other path
* please
* this is the one
* this is it
* this should work
* try reverting that change that might not be needed
* remove appveyor testing scaffolding
Co-authored-by: Jennifer Shehane <jennifer@cypress.io>
* Remove unused stuff
* Fix eslint errors
* Use local cypress running script
* Fix dependency resolution
* Revert "Fix dependency resolution"
This reverts commit 01a70be211.
* Add @cypress/react CI
* Properly resolve @types pacakges
* Run tests with mocha
* Fix cypress tests
* Fix or skip some specs
* Add retries to the card-spec.js
* Remove jest mocks
* Run e2e examples on CI
* Fix yarn cache key
* Fix e2e examples jobs
* Rename cypress-react-unit-test with @cypress/react
* Fix circleci.yml
* Revert "Fix e2e examples jobs"
This reverts commit efcc7c4d19.
* Revert " Rename cypress-react-unit-test with @cypress/react"
This reverts commit 4febfcc82b.
* Replce cypress-react-unit-test with @cypress/react
* Persist build artifacts
* Fix working directory paths circle.yml
* Fix more CI
* adding yarn.lock files
* Make package.json for folder
* Remove .npmrc
* Update circle.yml
* Remove unused files
* Copy plugins files to the "dist" folder
* Fix links to the github repos
* Move init wizard from npm/react/init to npm/wizard
* Move init wizard from npm/react/init to npm/wizard
* Implement initial vue template
* Run wizard tests on CI
* Refactor continue: bool to success: bool for better code readability
* Fix circleci.yml
* Use only absolute paths for tests
* Stub process.exit calls
* Remove useless comments
* Add installation cypress to the wizard logic
* More improvements
* Include packages/examples/cypress into git
* Commit new files
* Use packages/example as SST for generated files
* Last improvements for wizard
* Update packages/server/lib/scaffold.js
* Rename wizard to create-cypress-tests
* Fix circleci config
* Fix snapshot tests
* Run all create-cypress-tests on ci
* Do not install plugins and scaffold files from kitchensink
* Ignore integration/examples folder for packages/example
* Run create-cypress-tests-tests on CI
* Add copy example cross-platform script
* Use copy example script in tests
* feat: create-cypress-tests auto-inject config (#9116)
* Implement the basic babel code transformation for configs
* Add more tests for edge-cases
* Add snapshot tests for autogenerated code for each template
* Add git status guard
* Add git status guard
* Fix last test
* Fix tests
* Revert changes for packages/example
* Revert changes for packages/example/tsconfig.json
* Prepeare package for the release
* Fix inquirer name
* v0.0.125
* v0.0.127
* v0.0.128
* v0.0.130
* v0.0.131
* Add more UX features
* Add vue-cli template
* Make src as default folder for vue-cli template
* Revert dev-time changes
* Run appveyour windows build
* Run full appveyour build
* Fix circle.yml
* Update plugins
* Join paths for windows
* Revert example/lib changes
* Fix tests
* Revert unnecessary changes
* Implement dev-server dependency installation
* Update npm/create-cypress-tests/README.md
* Include webpack-options template in dist
Co-authored-by: Jessica Sachs <jess@jessicasachs.io>
* enable using yarn
* enable lerna and yarn workspaces
No longer can reliably access node_modules via thei node_modules directory; yarn may optimize it via hoisting it up. This meant updating JS tasks that were copying files directly from node_modules directories. In these cases, pulled in a new package to resolve these correctly.
SCSS files remain impacted, but cannot easily import via JS. These paths have been modified, but it feels dangerous and incorrect to reach into a node_module to grab files like this.
Many prebuild steps were removed. I **think** the purpose of `check-deps-pre` is no longer needed, but need to confirm this.
* enabling test-unit script
removal of pretest-unit due to check-deps-pre
* removal of all `check-deps` and `check-deps-pre`
I do not think these are needed anymore
* remove npm run all
Replaced by `lerna run` and `lerna run --scope`
* use yarn in circle CI
appveyor to soon follow
* yarn in appveyor
* remove need for bin-upplaces using bin-up have a dev dependency on some package; mostly mocha. This mocha package will be optimized by yarn workspaces by hoisting it into the root; which is effectively what bin-up usage was mimicing.
* replace npm run with yarn in package files
* replace explict paths to internal packages with yarn bin
* remove unecessary link packages script and references
* properly require package for mocha
* removing yarn test in this package as it was just a proxy for test-*
* yarn test in root now reflects what is run in circle ci
* relax yarn version requirement for circle ci
* @packages/cli is really just cypress
also run test in parallel via `yarn test`; it runs test in all 10 packages
* ensure postinstall is called before prebuild
yarn does not call postinstall when nothing has installed; such is the case when everything has been cached
* vscode config uses yarn
* cannot rely on which node_modules dir a package is in
find the right node_module dir via `resolve-pkg`
* further relax yarn version for OSX build in circle ci
* resolve failing test
Regarding direct access to node_modules
* node version in mac build not sufficient
ignoring check of node/yarn versions when installing
* preinstall script does not exist
I **think** the reason to not install packages' modules (the reason for `--ignore-scripts` may be irrelevant with yarn workspaces managing the packages)
* upgrade mocha that was using --file
`--file` was introduce in >=5
* scope test runs to correct packages
* explictly close connections; otherwise script hangs after tests run
* refactor so npm and npx commads can be created
npx is used to utlize lerna for running across all packages sans cli
* properly resolve socket.io-client node_module
We cannot reach directly into node_modules to grab the socket.io-client file. Furthermore, running it locally will require resolving from a different cwd, the repo root, as opposed to the package's dist directory.
The existence of the file deterimes whether we are building the binary or running locally.
* remove unnecessary arg in vscode debug config
enable debugging in @packages/server to troubleshoot failing test
* another npm command found to be changed to yarn
* properly print colors to terminal
`lerna run` does not appear to print colors to the terminal properly. Changed to leverage `lerna exec`
See https://github.com/lerna/lerna/issues/1168
* add missing test scripts to packages that have partially have them
'test', 'test-unit', 'test-watch', and 'test-debug'
This makes running them from the root easier and enables debugging via IDE on more packages
* properly patch package in yarn workspaces
* another package needing to postinstall
* use existing script over explicit lerna exec
* patches must be copied to dist
* return to building on postinstall
* do not hoist driver's packagesThere are too many places we need driver's packages to not be hoisted when testing. We have *.html files in test with script tags srcing node_modules.
* wait-on is used in circle-ci and needs to be a root dep
No longer hoisted by `@packages/driver`. This previously worked only because it was hoisted. Adding it to root properly.
* update documentation based on new ergonomics
* launcher has unit tests that should be runnable via top level task
* more concise way to run build within cypress scope
* fix for unit test that never seemed to work
`getPathToExample` is really `getPathToExamples`
* bust cache based on yarn.lock changing
* define intra-dependencies among packages
Due to the way we build the binary, all are considered dev dependencies.
* address `jquery.scrollto` mismatched jquery version
Tell yarn to explicitly resolve `jquery@3.1.1` for any dependencies and sub-dependencies. The root issue is that `jquery.scrollto` package specifies jquery as a dependency instead of a peer dependency (which is correct). Its jquery version is set to the `>=1.8` which then resolves to 3.4.1. In doing so, it will patch its jquery instead of ours; meaning that `$.scrollTo` is not defined.
* add/remove deps from renovate
- bin-up is gone in favor of yarn workspaces and lerna from root
- check-deps is gone in favor of `yarn check --integrity`
- lerna added
* few misc yarn lock updates
* hope that this may speed up build binary
installing several of the same dep in >1 package will likely be sped up using yarn due to its machine-wide caching.
* yarn pack prefix version with a `v`
* auto-run `yarn install` when deps become out of date
When switching to a branch with a different set of required deps, running any of the main top level tasks (as seen in the `./CONTRIBUTING.md` guide) will check for deps changes via `yarn check --integrity` and run `yarn` in root if deps are out of sync.
* add clean top level task, remove prebuild
install => build => prebuild => check => install === no good
* address code review to undo formatting changes
* favor default imports over deconstructing imports
* favor @package resolution; pr feedback
* include a specific revision
for some reason, it cannot resolve the original SHA `29dafed297142d3b8a9d8a01842cbdf249a98b72`
using the next closes SHA
* properly cache yarn packagesfollowed guide: https://circleci.com/docs/2.0/yarn/
* lower barrier for contributors to get started
relax node version to be 12.0.0 or higher; will use node version found in `.node-version` in CI
* updates required after merging latest development
was getting type errors when building. recreating the `yarn.lock` file seemed to resolve the issue.
* hidden dep on a specific type version in server
made dep explicit and now it can build.
* update request to patched version
non-breaking changes to request was updated in server, but not everywhere else. It appears that transitive deps were using the 2.88.0 request version instead of the updated one for the server package.
* missing commit from previous commit/merge
* do not force a higher version of yarn than the default on circleci
* exclude e2e.js helper from stop-only command
* trying to bust node_modules cache.https://github.com/yarnpkg/yarn/issues/6412#issuecomment-537787740
* incorrect quotation tick placement
* fix: properly postinstall parse-domain
Do not explicitly script the shell invocation of a dependency's postinstall (parse-domain). The dependency's node_modules may not be where the package thinks they are and are not properly resolved.
It appears that postinstall will automatically be called when installing with yarn.
* run all CI stages
* fix win-appveyor-build.js
* Update CONTRIBUTING.md
Co-Authored-By: Zach Bloomquist <github@chary.us>
* Update CONTRIBUTING.md
Co-Authored-By: Zach Bloomquist <github@chary.us>
* Update CONTRIBUTING.md
Co-Authored-By: Zach Bloomquist <github@chary.us>
* Server package watching a specific test works correctly.
* PR feedback
* Correctly use yarn to pack (to get package size)
* correct size calculation
`yarn pack` does not output the file name like `npm pack` does. Correct this by explictly setting the filename.
* PR feedback
* PR feedback
* update readmes and testing commands from them
* do not include this in default build
* yarn is now installed by default
https://github.com/appveyor/ci/issues/1852
* do not include server in `yarn` auto build
* a few more npm references changed to yarn
* Revert "run all CI stages"
This reverts commit 9256aed99f.
* Update circle.yml
Co-Authored-By: Zach Bloomquist <github@chary.us>
Co-authored-by: Zach Bloomquist <github@chary.us>
* move github templates into .github folder
* move code of conduct
* add pull request review comments
* fix a few missed links to newly moved github resources
Co-authored-by: Jennifer Shehane <jennifer@cypress.io>
* fix(doc): fix 404 link
The `example_spec.js` has been split up so we redirect to the corresponding directory
* Updated a few references from example_spec -> example tests [skip ci]
* Update onboarding dialog to handle new kitchen-sink examples
- Now display ‘integrationExampleFolder’ in messaging instead of file
- Does not display children files of ‘examples’ folder (it’s way too
much) and instead shows ‘examples’ as a closed folder in preview
- Reworded onboarding message to grammatically make sense with folder
- updated finder to open ‘integrationExampleFolder’
- update fixture to reflect new kitchen sink structure.
* bump kitchensink example to 1.0.0
* handle multiple spec files when converting kitchen-sink to example
* handle multiple example spec files when scaffolding
* handle multiple example files in desktop-gui
* update unit tests for new example specs
* fix integration spec
Mike McCready