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
For some cases (case5 and case6) the emitted .d.ts files contains a path to node_modules, which is not needed and when published to NPM as part of my library will not resolve correctly.
case5 and case6 work the same as all others, just having methodName(init?: LionRequestInit | undefined): void;
Additional information about the issue
I'm using case6 to define method types without overriding it, because it's indirectly supporting smth that the parent class does not. So I'm intertested to make it work. Workarounds like case2-3-4 are not suitable for me.
The text was updated successfully, but these errors were encountered:
π Search Terms
"JSDoc", "typedef", "node_modules", "resolved"
π Version & Regression Information
β― Playground Link
https://stackblitz.com/edit/issue-ts-jsdoc-typedef-resolved-node-modules?file=issue.js,dist-types%2Fissue.d.ts
In the StackBlitz example you can run
npm run build:watch
to play with the input and output ofissue.js
.π» Code
π Actual behavior
For some cases (
case5
andcase6
) the emitted.d.ts
files contains a path tonode_modules
, which is not needed and when published to NPM as part of my library will not resolve correctly.π Expected behavior
case5
andcase6
work the same as all others, just havingmethodName(init?: LionRequestInit | undefined): void;
Additional information about the issue
I'm using
case6
to define method types without overriding it, because it's indirectly supporting smth that the parent class does not. So I'm intertested to make it work. Workarounds like case2-3-4 are not suitable for me.The text was updated successfully, but these errors were encountered: