Skip to content

Conversation

@elliot-huffman
Copy link

Fix an issue where the types are not correctly linked to. They generate in the dist/src folder, not in the dist folder.

Fixes #85379

What?

Types are not propagating via imports.

Why?

Type Definition files are not being linked to properly.
The type def files are generating in a sub folder, src not in the dist folder.

How?

Incorrect package.json configuration, the types' path is not correct.

Fix an issue where the types are not correctly linked to. They generate in the `dist/src` folder, not in the `dist` folder.
@elliot-huffman elliot-huffman changed the title Fix Types Incorrect eslint-config-next Type Export - Fix Oct 26, 2025
@ijjk
Copy link
Member

ijjk commented Oct 26, 2025

Allow CI Workflow Run

  • approve CI run for commit: 71789c4

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

1 similar comment
@ijjk
Copy link
Member

ijjk commented Oct 26, 2025

Allow CI Workflow Run

  • approve CI run for commit: 71789c4

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

@ohkimur
Copy link

ohkimur commented Oct 28, 2025

This seems similar with #84929 which is open before this one.

@ztanner I saw you did the latest release. Is it possible to ensure one of these 2 PR's will be included in the next release? At the moment I had to patch the package in order to use it properly in ts as I already described in #84929. I'd really appreciate if we can make this go through so I don't maintain my own patched version of the package 😅. I'm sure others would appreciate it too ☺️.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Incorrect eslint-config-next Type Export

3 participants