Skip to content

Unresolved imports should error in fenced code blocks #1659

Open
@mbostock

Description

@mbostock

We translate static imports to dynamic imports, but this should error rather than resolve to undefined:

import {doesNotExist} from "./module.js";

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn’t working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions