-
-
Notifications
You must be signed in to change notification settings - Fork 750
Fix the package types exports #5204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
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)