Skip to content

Importing Types resolving into nothing (declaration re-export inference issue) #14

@vestrepra

Description

@vestrepra

Working with the toolkit has been great, just I noticed an issue I can't get around, tried to resolve on my end but still seems the core issue is with the library and how Types are exported.

Importing functions works fine, but as you can see down below, when I try to import a type, it's valid import, but it resolves into nothing and I can't use it for typechecking. This is the case for every type I try to import. I also tried without type keyword.

Image

After some tinkering, I also found that within node_modules/@azuro-org/toolkit when I go in index.d.ts and check the type, it's the same empty type.

Image

Other packages I import types from like express are acting fine and referencing correctly, only for this package its not working as expected.

My workaround was to import directly from the file the type is exporting from, this worked as seen in the screenshot (mind the alias I did to access types directly from the package)

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions