Skip to content

Transformed code is leaving type imports with npm: prefixes #1186

@camflan

Description

@camflan

JSR is transforming files import statements and is leaving npm: prefixes on import type {}... statements instead of deprefixing.

Changing the import statement from import type {}... to import {}... fixes the issue

Expected,

import type { MyType } from "my-npm-module-name";
import { MyClass } from "my-other-npm-module-name":

Received,

import type { MyType } from "npm:my-npm-module-name";
import { MyClass } from "my-other-npm-module-name":

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Needs Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions