Fix the package types exports

[epszaw]

Motivation/Description of the PR

It's not possible to correctly build codeceptjs custom reporters after the package update.

The PR provides a correct exports field that no longer overrides types field and make possible to use types without collisions.

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 fixes TypeScript type resolution issues in the codeceptjs package by restructuring the exports field in package.json to properly support both CommonJS and ES modules while maintaining correct type definitions.

• Restructured the exports field to use conditional exports with explicit import/require/types mappings
• Moved the top-level types field above exports to ensure proper fallback behavior
• Added module field for ES module compatibility

---

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

[epszaw]

Hey, @kobenguyent! Thank you for the merge. When do you plan to make the next release? Without the change, it's not possible to develop integrations for codeceptjs 3.7.x.

[kobenguyent]

hey @epszaw we haven't got concrete plan for the next release, but I guess you could try https://un5gmtkzgjp82ya0h3u28.julianrbryant.com/package/codeceptjs/v/3.7.6-beta.1?activeTab=code as this included your fix. Thanks!

[epszaw]

Awesome, thank you!