Skip to content

No location of parse error reported #186

@piotr-dobrogost

Description

@piotr-dobrogost

I was not getting location of parse error and inspecting err object (

} catch (err) {
) revealed it has loc attribute – holding both line and column of parse error – instead of lineNumber and column properties used currently.

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