Skip to content

Linked dependencies resolves to file system path #45109

Closed
@Muritavo

Description

@Muritavo

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.58.0
  • OS Version: MacOS 11.4 (Big Sur)

Obs: Not related to OS, as other OSs have the same problem

Steps to Reproduce: (A reproducible cenario can be found here)

  1. Use the link feature of npm to link a dependency to a local copy by using a symbolic link
yarn link SOME_DEPENDENCY
  1. Now when using the intellisense feature to auto import, it resolves the dependency to the relative filesystem path instead of the node_modules require path.
    For example:
// Instead of resolving as a require path
import {something} from "dependency/something";

// It resolves to the relative path
import { something } from "../../../../some/unrelated/path/dependencyFolder/something"

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions