# eslint: Fix \`workspaceFolder.uri\` sent as raw path instead of \`file:/… \(\#54383\) · gitcafe/zed

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

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

Visibility: public

Requested revision: 7fcc4ba3438e3ea8a2d1c436090a88fc8c853b6c

Requested commit: 7fcc4ba3438e3ea8a2d1c436090a88fc8c853b6c

Commit: 7fcc4ba3438e3ea8a2d1c436090a88fc8c853b6c

Tree: c00a53f2bc4562ba317dc2619c4511ec2113863c

Author: YangChengxxyy

Committer: GitHub

## Message

```
eslint: Fix `workspaceFolder.uri` sent as raw path instead of `file:/… (#54383)

…/` URI

The ESLint adapter was sending `workspaceFolder.uri` as a raw filesystem
path (e.g. `/Users/foo/project`) instead of a proper `file://` URI (e.g.
`file:///Users/foo/project`).

This caused the vscode-eslint server's `workingDirectory: { mode: "auto"
}` to fail when resolving the workspace root, falling back to the linted
file's directory as the working directory. As a result,
`eslint-import-resolver-typescript` could not locate `tsconfig.json`,
breaking path alias resolution for rules like `import/order` — producing
different lint results compared to VS Code.

Self-Review Checklist:

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


Release Notes:

- N/A or Added/Fixed/Improved ...
```

## Parents

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

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