Cypress App example updates related to Cypress 14 (#30)

* delete vue2 and nuxt2 projects (#27)

* remove nextjs 12 and 13 projects. add nextjs 14 project (#25)

* chore: update svelte-vite-ts to svelte 4 and vite 5 (#28)

* update angular regular (modules/ not standalone) with generated ng new angular --no-standalone and updated standalone (#31)

* chore: remove cra examples with cypress 14 (#32)

* chore: remove vuecli apps (#33)

* chore: remove vuecli apps

* make sure webpack app is working (now running as expected)

* update svelte-webpack-ts to Svelte 4 (#34)

* chore: add next 15 example (#37)

* chore: update angular-standalone to v19 (need prebuilt binary to work) (#38)

* chore: update vite to vite 6. svelte-vite project needs to wait until we support svelte 5 (#39)

* chore: update svelte projects (vite and webpack) to svelte 5 (#40)

* update svelte-webpack to support svelte 5

* update tests and components to be svelte 5 compliant

* update svelte vite project to svelte 5 and update tests/components to comply with svelte 5

* chore: update to react 19 and update react 19 webpack project (#41)

* update to react 19. Additionally, update react webpack project to use latest dependencies

* Update react-webpack5-js/package.json

Co-authored-by: Ryan Manuel <[email protected]>

---------

Co-authored-by: Jennifer Shehane <[email protected]>
Co-authored-by: Ryan Manuel <[email protected]>

* chore: merge main into release 14 (#42)

* chore: update react-webpack5-js app (#36)

* update cypress to use 14 prerelease

* chore: update react-webpack5-js app (#36) (#43)

* chore: update binaries to use published Cypress 14 binary (#45)

---------

Co-authored-by: Matt Schile <[email protected]>
Co-authored-by: Ryan Manuel <[email protected]>
Co-authored-by: Jennifer Shehane <[email protected]>

Author: 4 people

angular-standalone/.editorconfig

@@ -10,6 +10,7 @@ trim_trailing_whitespace = true
 
 [*.ts]
 quote_type = single
+ij_typescript_use_double_quotes = false
 
 [*.md]
 max_line_length = off

angular-standalone/README.md

@@ -1,27 +1,59 @@
 # AngularStandalone
 
-This project was generated with [Angular CLI](https://github.com/angular/angular-cli) version 18.0.2.
+This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.1.
 
 ## Development server
 
-Run `ng serve` for a dev server. Navigate to `http://localhost:4200/`. The application will automatically reload if you change any of the source files.
+To start a local development server, run:
+
+```bash
+ng serve
+```
+
+Once the server is running, open your browser and navigate to `http://localhost:4200/`. The application will automatically reload whenever you modify any of the source files.
 
 ## Code scaffolding
 
-Run `ng generate component component-name` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module`.
+Angular CLI includes powerful code scaffolding tools. To generate a new component, run:
+
+```bash
+ng generate component component-name
+```
+
+For a complete list of available schematics (such as `components`, `directives`, or `pipes`), run:
+
+```bash
+ng generate --help
+```
 
-## Build
+## Building
 
-Run `ng build` to build the project. The build artifacts will be stored in the `dist/` directory.
+To build the project run:
+
+```bash
+ng build
+```
+
+This will compile your project and store the build artifacts in the `dist/` directory. By default, the production build optimizes your application for performance and speed.
 
 ## Running unit tests
 
-Run `ng test` to execute the unit tests via [Karma](https://karma-runner.github.io).
+To execute unit tests with the [Karma](https://karma-runner.github.io) test runner, use the following command:
+
+```bash
+ng test
+```
 
 ## Running end-to-end tests
 
-Run `ng e2e` to execute the end-to-end tests via a platform of your choice. To use this command, you need to first add a package that implements end-to-end testing capabilities.
+For end-to-end (e2e) testing, run:
+
+```bash
+ng e2e
+```
+
+Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.
 
-## Further help
+## Additional Resources
 
-To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.
+For more information on using the Angular CLI, including detailed command references, visit the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.

angular-standalone/angular.json

@@ -46,8 +46,8 @@
                 },
                 {
                   "type": "anyComponentStyle",
-                  "maximumWarning": "2kB",
-                  "maximumError": "4kB"
+                  "maximumWarning": "4kB",
+                  "maximumError": "8kB"
                 }
               ],
               "outputHashing": "all"

angular-standalone/cypress/support/component.ts

@@ -19,7 +19,7 @@ import './commands'
 // Alternatively you can use CommonJS syntax:
 // require('./commands')
 
-import { mount } from 'cypress/angular-signals'
+import { mount } from 'cypress/angular'
 
 // Augment the Cypress namespace to include type definitions for
 // your custom command.