fix(exports): resolve issues with module imports and requires #3428
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses a regression introduced in
pg@8.15.1
due to the addition of ESM support via #3423. The updatedexports
field inpackage.json
restricts access to internal modules such aslib/connection-parameters.js
, which are utilized by tools like node-pg-migrateAs a result, users such as salsita/node-pg-migrate#1398, #3429, #3431, possibly #3430 (couldn't replicate) encounter the following or similar errors:
To resolve this, I've updated the
exports
field to include./lib/*
, ensuring compatibility with existing tools that rely on them.