Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 2 additions & 12 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -23,19 +23,8 @@
"types": "./dist/index.d.ts",
"default": "./dist/index.js"
},
"./*": {
"types": "./dist/*.d.ts",
"default": "./dist/*.js"
},
"./package.json": "./package.json"
Comment on lines 23 to 26

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Potentially breaking removal of wildcard subpath exports

Dropping the ./* export map entry and typesVersions wildcard prevents consumers from importing any sub-path other than the package root (e.g. import x from '@antelopejs/interface-mongodb/some-module' will now throw ERR_PACKAGE_PATH_NOT_EXPORTED). If any downstream code relies on these paths, this is a breaking change. The PR is labelled chore and the version remains 0.0.2, so there is no semver signal to consumers that a breaking change was shipped. If sub-path imports were never intended to be part of the public API, a note in the changelog or a minor version bump would communicate the intent clearly.

Prompt To Fix With AI
This is a comment left during a code review.
Path: package.json
Line: 23-26

Comment:
**Potentially breaking removal of wildcard subpath exports**

Dropping the `./*` export map entry and `typesVersions` wildcard prevents consumers from importing any sub-path other than the package root (e.g. `import x from '@antelopejs/interface-mongodb/some-module'` will now throw `ERR_PACKAGE_PATH_NOT_EXPORTED`). If any downstream code relies on these paths, this is a breaking change. The PR is labelled `chore` and the version remains `0.0.2`, so there is no semver signal to consumers that a breaking change was shipped. If sub-path imports were never intended to be part of the public API, a note in the changelog or a minor version bump would communicate the intent clearly.

How can I resolve this? If you propose a fix, please make it concise.

},
"typesVersions": {
"*": {
"*": [
"dist/*.d.ts"
]
}
},
"scripts": {
"build": "rimraf dist && tsc",
"format": "biome format --write .",
Expand All @@ -57,5 +46,6 @@
},
"publishConfig": {
"access": "public"
}
},
"antelopeJs": {}
}
Loading