Fix Zed Extension breaking when package.json is not present in workspace root

[mizdra]

close: #217

Cause of the bug

When opening a workspace without package.json in zed, get_ts_plugin_root_path returns Err(_) in the following line.

css-modules-kit/crates/zed/src/lib.rs

Line 35 in 5408682

let package_json = worktree.read_text_file("package.json")?;

Then, worktree.root_path() is set as the starting location for searching for ts-plugin in the following line.

css-modules-kit/crates/zed/src/lib.rs

Line 110 in 5408682

"location": self.get_ts_plugin_root_path(worktree)?.unwrap_or_else(|| worktree.root_path()),

worktree.root_path() is the root directory of the workspace. However, the ts-plugin is typically not installed in that directory. The Zed Extension for css-modules-kit installs the ts-plugin in extension_work_dir (on macOS, this is ~/Library/Application Support/Zed/extensions/work/css-modules-kit).

Solution

We change it so that extension_work_dir is used as the starting location for searching for ts-plugin.

Changelog

• feat: supports CMK_LOAD_LOCAL_TS_PLUGIN for loading local ts-plugin
• fix: fix Zed Extension breaking when package.json is not present in workspace root

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5e0fffd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR