You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Unable to bundle types from dependency while importing from root but works for sub-path modules #411
The weird thing is if I import types from my-kit (./node_modules/my-kit/dist-types/index.d.ts). It will come into being a relative path import statement from ./types (but there no dist/types/index.d.ts or somethings like it in there).
But I expected it should be bundle into the dist/index.d.ts just like if I import the some type from the sub-path module my-kit/plugin (./node_modules/my-kit/dist-types/types/plugin.d.ts). It would be seems like:
Activity
Timeless0911 commentedon Nov 25, 2024
same as #470
If I write full
indexpath like below, it work as expected.Asuka109 commentedon Nov 25, 2024
It sounds like a ES Module limitation or something which won't resolve any directory as a module by appending
./index...fi3ework commentedon Nov 25, 2024
type-festis shipped in CJS mode, so api-extractor should follow Node.js resolution strategy, which should handles/index.Timeless0911 commentedon Nov 26, 2024
Tracking microsoft/rushstack#5018