Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Yarn 2 Plug'n'Play recognition based on location of parser package, rather than file being linted #3293

Closed
Labels
awaiting responseIssues waiting for a reply from the OP or another partypackage: parserIssues related to @typescript-eslint/parser
@WesCossick

Description

@WesCossick
  • I have tried restarting my IDE and the issue persists.
  • I have updated to the latest version of the packages.
  • I haveread the FAQ and my problem is not listed.

Repro

https://github.com/WesCossick/demonstrate-typescript-eslint-bug

Expected Result

For the@typescript-eslint/parser package to recognize that theproject-to-lint/ directory is using Yarn 2 with Plug'n'Play.

Actual Result

The@typescript-eslint/parser package is assuming that, since it is located in a directory that's using Yarn 1, that theproject-to-lint/ directory is also using Yarn 1. Therefore, it can't seem to find any imports, because presumably, it's looking for anode_modules/ directory, which doesn't exist.

Additional Info

UsingNode.js API, which doesn't offer--debug flag or equivalent option.

Versions

packageversion
@typescript-eslint/parser4.22.0
TypeScript4.2.4
ESLint7.24.0
node14.16.1

Metadata

Metadata

Assignees

No one assigned

    Labels

    awaiting responseIssues waiting for a reply from the OP or another partypackage: parserIssues related to @typescript-eslint/parser

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp