D
Deno
Can symbol documentation be detected when re-exported from top level default export? - Deno
T
Deno
β’
15mo ago
β’
3 replies
tylersayshi
Can symbol documentation be detected when re-exported from top level default export?
I am working on a promise util library here
:
https://jsr.io/@tyler/duckhawk@0.1.0
I have documented my first util with jsdoc
, but re
-exporting this symbol from a top level default export seems to break the jsr auto
-doc detection
.
Update
: It seems like exporting as a single default object results in the wrong type output too
, which seems related
. The type of default is
{}
{}
.
The index
.ts is just like this
:
import
{ map }
from
'./map.ts'
;
export
default
{ map };
import
{ map }
from
'./map.ts'
;
export
default
{ map };
JSR
@tyler/duckhawk - JSR
@tyler
/duckhawk on JSR
: native Promise based implementations of bluebird utilities
Deno
Join
Chat about Deno, a modern runtime for JavaScript and TypeScript.
20,934
Members
View on Discord
Resources
ModelContextProtocol
ModelContextProtocol
MCP Server
Recent Announcements
Similar Threads
Was this page helpful?
Yes
No
Similar Threads
Top level awaits for `import()`
S
slabcache / help
3y ago
Default export has no call signatures
J
jordanbtucker / help
2y ago
Good way to re-export with document?
N
Nanashi. / help
2y ago
Deno dependency top level await work around
W
weegee / help
3y ago