Skip to content

Consider caching output of deno info #1

@bartlomieju

Description

@bartlomieju

I suggest to cache the output of deno info when it is called during resolve/load stage. If the root module that was passed to deno info is loaded then all of its imports (and imports of imports) would be loaded as well, so it seems wasteful to call out to deno info for every single file, instead we could reach out for the information that was already retrieved in the first call to deno info.

I think it's fine to never invalidate this cache as Vite will reload on file change which (if I'm not mistaken) should invalidate the cache.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions