Skip to content

Treat trailing-slash exports keys as wildcards - #283

Open
morgan-coded wants to merge 1 commit into
arethetypeswrong:mainfrom
morgan-coded:fix/136-trailing-slash-wildcards
Open

morgan-coded wants to merge 1 commit into
arethetypeswrong:mainfrom
morgan-coded:fix/136-trailing-slash-wildcards

Conversation

@morgan-coded

Copy link
Copy Markdown
Contributor

exports keys ending in / were treated as literal entrypoints and reported as NoResolution under node16 and bundler resolution.

I treated those keys as wildcards alongside * keys, so they display as (wildcard) and skip the resolution check.

Explicit --entrypoints and --include-entrypoints values ending in / receive the same wildcard treatment.

The new folder-mapping test fails before the fix and passes with it, and the core and CLI suites pass without snapshot changes; this addresses #136.

A "./dir/" exports key is a folder mapping equivalent to "./dir/*", so
mark it as a wildcard instead of resolving it as a literal subpath.
@changeset-bot

changeset-bot Bot commented Sep 13, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 1ae5886

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
@arethetypeswrong/core Patch
@arethetypeswrong/cli Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant