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
I'd really like to add support for declaration maps so that in my VS Code I can use Go-to-Definition to navigate to the .ts files instead of .mts or .mjs files.
What I've tried to do:
Add "declaration": true and "declarationMap": true to packages/openai-partial-stream/tsconfig.json.
Run npm run build.
Still, no .map files were generated.
Since the npm run build uses tsup, I suspect it's related to egoist/tsup#488 and apparently this remains unsupported. I'd love to hear your thoughts. I'm happy to help.
The text was updated successfully, but these errors were encountered:
Hi, thanks for your suggestion and for trying to fix this. I'm all for making the developer experience better. I need to check if tsup supports this or not, but seems based on the open issue your shared about tsup it doesn't, I'll have to look into what we can do about it.
I'd really like to add support for declaration maps so that in my VS Code I can use Go-to-Definition to navigate to the .ts files instead of .mts or .mjs files.
What I've tried to do:
"declaration": true
and"declarationMap": true
to packages/openai-partial-stream/tsconfig.json.npm run build
.Since the
npm run build
uses tsup, I suspect it's related to egoist/tsup#488 and apparently this remains unsupported. I'd love to hear your thoughts. I'm happy to help.The text was updated successfully, but these errors were encountered: