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 example, I am packaging a toolkit for my own use, using export * from "is-what"
can not export all types and pass them through to the new package, although there is no type prompt,
but js functions can be used normally
I wonder if this is a type definition flaw in Is-what
The text was updated successfully, but these errors were encountered:
biggerstar
changed the title
export * from "is-what" No type exportexport * from "is-what"
export * from "is-what" No type export
Jun 22, 2024
For example, I am packaging a toolkit for my own use,
using export * from "is-what"
can not export all types and pass them through to the new package, although there is no type prompt,
but js functions can be used normally
I wonder if this is a type definition flaw in Is-what
The text was updated successfully, but these errors were encountered: