Skip to content

[DDC] Broken source maps when running with the hot reload-able module system #60474

Open
@nshahan

Description

@nshahan

Stack trace mapping is broken for flutter run -d chrome --web-experimental-hot-reload.

Throwing an exception or creating a stack trace should have properly mapped source locations. Currently you see all JavaScript source locations.

This is likely due to the stack trace mappers use of the dart:_runtime method trackLibraries().

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1A high priority bug; for example, a single project is unusable or has many test failuresarea-web-jsIssues related to JavaScript support for Dart Web, including DDC, dart2js, and JS interop.web-dev-compilerweb-hot-reloadIssues related to stateful hot reload on the web

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions