Skip to content

fix(exports): expose ./package.json in the exports map - #16

Closed
cldmv-bot[bot] wants to merge 4 commits into
nextfrom
fix/exports-package-json
Closed

fix(exports): expose ./package.json in the exports map#16
cldmv-bot[bot] wants to merge 4 commits into
nextfrom
fix/exports-package-json

Conversation

@cldmv-bot

@cldmv-bot cldmv-bot Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

🚀 What's Changed

💥 Breaking Changes

No breaking changes

✨ Features

No new features

🐛 Bug Fixes

📦 Dependencies

No dependency updates

🔧 Other Changes

No other changes

👥 Contributors

Shinrai and others added 4 commits August 8, 2026 20:48
… invalid -C= form

The devcheck scanner (merged via #10) had two nits: the space-form branch
(`--conditions x` / `-C x`) consumed tokens[i+1] as the value but did not
advance the loop index, so a value that itself looks like a flag could be
double-processed; and it handled `-C=value`, which Node rejects outright
("bad option") so it can never appear. Advance i past the consumed value token,
drop the dead `-C=` branch (valid forms: `--conditions=x`, `--conditions x`,
`-C x`), and add -C short-flag test coverage.

Redo of the change that was mistakenly pushed onto the already-merged
fix/devcheck-condition-detection branch (which opened a diverged PR #12);
this branch is cut fresh from next so the diff is only the scanner delta.
Node's exports map is a strict allowlist: with only "." and "./main"
declared, `require.resolve("@cldmv/uuid/package.json")` (and any tool that
locates a package by resolving its package.json) throws
ERR_PACKAGE_PATH_NOT_EXPORTED. This broke @cldmv/rummage's web build.

Add the conventional `"./package.json": "./package.json"` entry so the
manifest is resolvable by name, and a regression test that asserts both the
exports entry and real Node self-resolution.

Fixes #6
@cldmv-bot cldmv-bot Bot added ! fix → next v4 flow: fix contributor PR targeting the next integration branch area: tests Touches test files, fixtures, or test infrastructure type: dependencies Relates to dependency updates, version bumps, or package management labels Aug 9, 2026
@Shinrai Shinrai closed this Aug 9, 2026
@Shinrai
Shinrai deleted the fix/exports-package-json branch August 9, 2026 04:44
@Shinrai

Shinrai commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

Closing — this branch was cut from a stale next (pre-v1.1.6 release), so the diff carried the already-shipped devcheck fix and version bump as phantom changes on top of the actual fix. Superseded by a clean branch off current next that contains only the ./package.json export + its regression test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: tests Touches test files, fixtures, or test infrastructure ! fix → next v4 flow: fix contributor PR targeting the next integration branch type: dependencies Relates to dependency updates, version bumps, or package management

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant