Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/api/node-events/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -233,7 +233,7 @@ You can use the `task` event to do things like:
## Execution context

The [`setupNodeEvents`](/app/references/configuration#setupNodeEvents)
function (or deprecated [plugins file][legacypluginsfile] function) is invoked
function is invoked
when Cypress opens a project.

Cypress does this by spawning an independent `child_process` which then
Expand All @@ -246,7 +246,7 @@ This code will be executed using the Node version that launched Cypress.

When Cypress executes the
[`setupNodeEvents`](/app/references/configuration#setupNodeEvents) function
(or deprecated [plugins file][legacypluginsfile] function) it will execute with
it will execute with
`process.cwd()` set to your project's path. Additionally - you will be able to
`require` **any node module** you have installed, including local files inside
your project.
Expand Down Expand Up @@ -289,7 +289,7 @@ itself runs in. That means you cannot accidentally modify or change Cypress's
own execution in any way.

If your [`setupNodeEvents`](/app/references/configuration#setupNodeEvents)
function (or deprecated [plugins file][legacypluginsfile] function) has an
function has an
uncaught exception, an unhandled rejection from a promise, or a syntax error -
Cypress will automatically catch those and display them to you inside of the
console and even in Cypress itself.
Expand Down