fix: max listeners exceeded warning

[kobenguyent]

Motivation/Description of the PR

• Description of this PR, which problem it solves
• Resolves #issueId (if applicable).

Applicable helpers:

• Playwright
• Puppeteer
• WebDriver
• REST
• FileHelper
• Appium
• TestCafe

Applicable plugins:

• allure
• autoDelay
• autoLogin
• customLocator
• pauseOnFail
• coverage
• retryFailedStep
• screenshotOnFail
• selenoid
• stepByStepReport
• stepTimeout
• wdio
• subtitles

Type of change

• 🔥 Breaking changes
• 🚀 New functionality
• 🐛 Bug fix
• 🧹 Chore
• 📋 Documentation changes/updates
• ♨️ Hot fix
• 🔨 Markdown files fix - not related to source code
• 💅 Polish code

Checklist:

• Tests have been added
• Documentation has been added (Run npm run docs)
• Lint checking (Run npm run lint)
• Local tests are passed (Run npm test)

[Copilot]

Pull Request Overview

This PR addresses Node.js "max listeners exceeded" warnings by increasing the maximum number of event listeners allowed on both the custom event dispatcher and the global process object.

• Increased max listeners limit from 50 to 200 for the custom event dispatcher
• Added safeguard to increase process max listeners to 200 when the method is available
• Updated @types/node dependency to use caret range for better version flexibility

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
lib/event.js	Increases max listeners limits and adds process listener configuration with safety check
package.json	Updates @types/node to use caret version range instead of exact version

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Pull Request Overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Pull Request Overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The MAX_LISTENERS constant should include a comment explaining why 200 was chosen as the limit and under what conditions this value might need adjustment.

Suggested change

	// The MAX_LISTENERS constant sets the maximum number of event listeners for the dispatcher and process.
	// The value 200 was chosen to prevent EventEmitter memory leak warnings in large test suites,
	// where many plugins, hooks, or reporters may register listeners. Adjust this value if you encounter
	// warnings about possible memory leaks, or if your project requires more listeners due to additional
	// extensions or integrations.

[Copilot]

This conditional check and process configuration should include a comment explaining why it's necessary and what specific warnings it prevents.

Suggested change

	// Increase process max listeners to prevent warnings for beforeExit and other events
	// Set process max listeners to avoid "MaxListenersExceededWarning" when many listeners are attached to process events (e.g., "beforeExit").
	// This is necessary in large test suites to prevent Node.js from emitting warnings about possible memory leaks.