# task: Support \`path\` property on VS Code npm tasks \(\#62044\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/1274a5dc258096794a30623b2bdc8fc7a24f7ec4)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 1274a5dc258096794a30623b2bdc8fc7a24f7ec4

Requested commit: 1274a5dc258096794a30623b2bdc8fc7a24f7ec4

Commit: 1274a5dc258096794a30623b2bdc8fc7a24f7ec4

Tree: de57ff9d71150608a67c86ded664c14c9197b931

Author: Levin Rickert

Committer: GitHub

## Message

```
task: Support `path` property on VS Code npm tasks (#62044)

# Objective

npm tasks in VS Code support a `path` property which works like
`options.cwd` but it's always relative to the workspace folder.

## Solution

`cwd` is being set based on `path` of npm tasks. If `options.cwd` is
also set, it wins over the `path` property. This matches the behavior of
VS Code.

## Testing

A new test case has been added, testing deserialization of `path` and
`options.cwd`.

## Self-Review Checklist:

- [x] I've reviewed my own diff for quality, security, and reliability
- [ ] Unsafe blocks (if any) have justifying comments
- [ ] The content adheres to Zed's UI standards
([UX/UI](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist)
and
[icon](https://github.com/zed-industries/zed/blob/main/crates/icons/README.md)
guidelines)
- [x] Tests cover the new/changed behavior
- [ ] Performance impact has been considered and is acceptable

---

Release Notes:

- Added support for `path` property on VS Code npm tasks
```

## Parents

- [2893b86b048a6e5877eb2f61dac97c172460ba07](https://git.cafe/gitcafe/zed/commit/2893b86b048a6e5877eb2f61dac97c172460ba07?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/1274a5dc258096794a30623b2bdc8fc7a24f7ec4?format=markdown)