Skip to content

URL that fails to resolve results in webpack:///undefined #2

@steinybot

Description

@steinybot

A non-file and non-http URL that cannot be resolved (such as an invalid relative path) results in a source of webpack:///undefined.

The result in the callback to resolve is undefined and so it passes to the next callback { source: undefined, content: "" }.

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