Skip to content

Incomplete diagnostics when importing a non-existing module #1334

@saulecabrera

Description

@saulecabrera

Version 0.10.0

Current behavior
When importing a non-existing module, the diagnostic is incomplete; it's missing the location. For the following unexisting import

import * as foo from './bar';

the compilation phase reports:

ERROR: import assembly/bar not found

Expected behavior
For the case described above, the compilation phase should report complete diagnostics about the missing module:

ERROR TS{CODE}: Cannot find module './bar'

import * as foo from './bar';

in <file>.asc(line, column)

I found this while doing some tests for the language server.

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