Skip to content

Support Sourcemaps for Dev #456

Open
@curran

Description

@curran

As a newcomer to the Unovis codebase, I want to be able to know the file and line number from which an error originated, so that I can figure out the cause.

Current behavior: in npm run dev, there seems to be no sourcemaps configured, so when an error occurs, it resolves to bundle.js, which is useless. Example:

image

Desired behavior: in npm run dev, the environment leverages sourcemaps to tell you where the error is coming from.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions