Skip to content

Bad coverage information when loaders are used #179

@simlu

Description

@simlu

Opening this so there is an actual issue tracked on this repo and to get some attention.


There is a problem when reporting test coverage while using loaders. I'm not going to go into too much detail here since I don't fully understand the issue and don't want to give incorrect information. However there is plenty to read up on.

Relevant tickets:


Why is this important to fix?
Using loaders and query string parameters is the only (reasonable) way to invalidate imports in esm. This makes it almost mandatory to use in test libraries.

Would be great if you could give some feedback! Cheers, L~

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