Uh oh!
There was an error while loading. Please reload this page.
Fix the package types exports - #5204
Conversation
There was a problem hiding this comment.
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.
Uh oh!
There was an error while loading. Please reload this page.
epszaw
commented
Sep 25, 2025
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 |
kobenguyent
commented
Sep 25, 2025
hey @epszaw we haven't got concrete plan for the next release, but I guess you could try https://www.npmjs.com/package/codeceptjs/v/3.7.6-beta.1?activeTab=code as this included your fix. Thanks! |
epszaw
commented
Sep 26, 2025
Awesome, thank you! |
Motivation/Description of the PR
It's not possible to correctly build codeceptjs custom reporters after the package update.
The PR provides a correct
exportsfield that no longer overridestypesfield and make possible to use types without collisions.Applicable helpers:
Applicable plugins:
Type of change
Checklist:
npm run docs)npm run lint)npm test)