Skip to content

The default "fileLocation": "relative" property for tasks does not work with npm tasks that use the "path" property #160771

@segevfiner

Description

@segevfiner

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

  • VS Code Version: 1.71.0
  • OS Version: macOS 12.15.1

Steps to Reproduce:

  1. Define any npm task that is in a subfolder using the "path" property, and define a problemMatcher that uses "fileLocation": "relative".
  2. It won't work, as the directory that it should be relative to will be the ${workspaceFolder} rather than the actual working directory of the npm script set by "path".

Metadata

Metadata

Assignees

Labels

bugIssue identified by VS Code Team member as probable bughelp wantedIssues identified as good community contribution opportunitiesinsiders-releasedPatch has been released in VS Code InsiderstasksTask system issuesverifiedVerification succeeded

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions