Skip to content

Change Request: Stop publishing declaration map files for espree #755

Open

Description

@sethamus

Which packages would you like to change?

  • espree
  • eslint-scope
  • eslint-visitor-keys

What problem do you want to solve?

eslint-scope and eslint-visitor-keys do not publish declaration map files, whereas espree currently does.

According to the tsup documentation, declaration maps are designed for navigating local source files within a monorepo. They are not intended to be included in published NPM packages.

What do you think is the correct solution?

Update the espree build configuration to disable the generation and publishing of declaration map files.

Participation

  • I am willing to submit a pull request for this change.

AI acknowledgment

  • I did not use AI to generate this issue report.
  • (If the above is not checked) I have reviewed the AI-generated content before submitting.

Additional comments

No response

Activity

  1. moved this to Needs Triage in Triageon Jun 8, 2026
  2. moved this from Needs Triage to Triaging in Triageon Jun 8, 2026
  3. fasttime commented on Jun 8, 2026

    @fasttime
    Member

    Makes sense to me. dist/espree.d.cts.map and dist/espree.d.ts.map were added in espree v11.1.0 in 5887c4d along with the TypeScript type definitions. Since those files may be consumed by bundlers or other tooling, it seems safer to defer excluding them until the next major release.

  4. moved this from Triaging to Ready to Implement in Triageon Jun 8, 2026
  5. lumirlumir commented on Jun 13, 2026

    @lumirlumir
    Member

    Since those files may be consumed by bundlers or other tooling, it seems safer to defer excluding them until the next major release.

    If so, maybe this issue is better marked as blocked until then? Or could the breaking change happen in the near future?

  6. fasttime commented on Jun 14, 2026

    @fasttime
    Member

    If so, maybe this issue is better marked as blocked until then? Or could the breaking change happen in the near future?

    Espree versions aren't tied to ESLint releases, so the change doesn't have to wait, but I'm not sure if we want to publish a new major release only to remove some files from the bundle. I'm going to mark this as blocked as a reminder to merge a pull request later.

  7. moved this from Ready to Implement to Blocked in Triageon Jun 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

  • Status
    Blocked

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions