···11+{
22+ "name": "Using fixtures to represent data",
33+ "email": "hello@cypress.io",
44+ "body": "Fixtures are a great way to mock data for responses to routes"
55+}
+19
cypress/plugins/index.js
···11+/// <reference types="cypress" />
22+// ***********************************************************
33+// This example plugins/index.js can be used to load plugins
44+//
55+// You can change the location of this file or turn off loading
66+// the plugins file with the 'pluginsFile' configuration option.
77+//
88+// You can read more here:
99+// https://on.cypress.io/plugins-guide
1010+// ***********************************************************
1111+1212+const { startDevServer } = require('@cypress/vite-dev-server');
1313+1414+/**
1515+ * @type {Cypress.PluginConfig}
1616+ */
1717+module.exports = (on, _config) => {
1818+ on('dev-server:start', options => startDevServer({ options }));
1919+};
+20
cypress/support/index.js
···11+// ***********************************************************
22+// This example support/index.js is processed and
33+// loaded automatically before your test files.
44+//
55+// This is a great place to put global configuration and
66+// behavior that modifies Cypress.
77+//
88+// You can change the location of this file or turn off
99+// automatically serving support files with the
1010+// 'supportFile' configuration option.
1111+//
1212+// You can read more here:
1313+// https://on.cypress.io/configuration
1414+// ***********************************************************
1515+1616+// Import commands.js using ES2015 syntax:
1717+import 'cypress-real-events/support';
1818+1919+// Alternatively you can use CommonJS syntax:
2020+// require('./commands')