@askdkc/dsh-lsp-server 0.1.5 → 0.1.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/CHANGELOG.md +6 -0
  2. package/README.md +15 -6
  3. package/docs/usage.md +5 -5
  4. package/package.json +28 -28
package/CHANGELOG.md CHANGED
@@ -2,6 +2,12 @@
2
2
 
3
3
  ## Unreleased
4
4
 
5
+ - Pin the LSP service, tool, and host peers to DSH `0.2.0-rc.1` so cached `next` metadata cannot install incompatible LSP rows.
6
+ - Require Node.js 22.19+ or 24+ to match DSH 0.2.0.
7
+ - Use the same DSH launcher for plugin installation and Web startup.
8
+
9
+ ## 0.1.5
10
+
5
11
  - Support DSH `0.1.7-rc.2` by updating the bundled LSP packages, host peer ranges, and isolated package verification.
6
12
 
7
13
  ## 0.1.3
package/README.md CHANGED
@@ -6,21 +6,30 @@ Supports PHP/Blade via **PHPantom**, TypeScript/JavaScript, Svelte, HTML, CSS, a
6
6
 
7
7
  ## Install
8
8
 
9
- Requires Node.js **22.18+** and DSH **0.1.7-rc.2 or a compatible later 0.1.x release**. Compatibility is tested against **0.1.7-rc.2**; later DSH releases require their own verification. The required `@deepseek-ai/dsh-lsp` and `@deepseek-ai/dsh-tool-lsp` packages are installed automatically. For PHP/Blade, install **PHPantom** with `phpantom_lsp` in `PATH`. The other language servers are included.
9
+ Requires Node.js **22.19+ (22.x) or 24+** and DSH **0.2.0-rc.1**. The DSH LSP packages and Node language servers install with this plugin. For PHP/Blade, install **PHPantom** so `phpantom_lsp` is in `PATH`.
10
10
 
11
- From npm:
11
+ Install from npm into the Web profile:
12
12
 
13
13
  ```sh
14
- npx @deepseek-ai/dsh@0.1.7-rc.2 plugin --profile web add @askdkc/dsh-lsp-server
14
+ dsh plugin --profile web add @askdkc/dsh-lsp-server@0.1.7
15
15
  ```
16
16
 
17
- Or from GitHub:
17
+ Or install from GitHub:
18
18
 
19
19
  ```sh
20
- npx @deepseek-ai/dsh@0.1.7-rc.2 plugin --profile web add github:askdkc/dsh-lsp-server
20
+ dsh plugin --profile web add github:askdkc/dsh-lsp-server
21
21
  ```
22
22
 
23
- If you run DSH from a source checkout with `pnpm dsh web`, use `pnpm dsh plugin --profile web add ...` instead.
23
+ If `plugin add` stops with `ERR_PNPM_IGNORED_BUILDS` for `core-js`, set the build decision in the **Web profile's** `~/.dsh/profiles/web/pnpm-workspace.yaml`. Running `pnpm approve-builds` from the harness project does not configure that profile. To skip the script, add or update:
24
+
25
+ ```yaml
26
+ allowBuilds:
27
+ core-js: false
28
+ ```
29
+
30
+ If the failed add already wrote the dependency, remove it with `dsh plugin --profile web remove @askdkc/dsh-lsp-server`, then repeat the add command using the same `dsh` launcher (for example, `pnpm dsh`). A dependency alone does not activate the plugin: confirm `@askdkc/dsh-lsp-server` appears in `dsh.profile.bundles` in the profile's `package.json`. See [installation troubleshooting](docs/usage.md#install) for details.
31
+
32
+ An older installed bundle such as `0.1.2` is skipped on DSH 0.2.0-rc.1. Upgrade it with the `plugin add` command above after 0.1.7 is published; the version exemption is not a compatibility fix. Start or restart Web with `dsh web`.
24
33
 
25
34
  [Configuration, tool usage, and troubleshooting](docs/usage.md)
26
35
 
package/docs/usage.md CHANGED
@@ -20,20 +20,20 @@ See the [installation commands](../README.md#install).
20
20
 
21
21
  The bundle adds `lsp`, `lsp-webstack-provider`, `tool-lsp`, and `tool-lsp-extra` rows. Its `@deepseek-ai/dsh-lsp` and `@deepseek-ai/dsh-tool-lsp` dependencies are installed automatically; do not install them separately. The harness still provides the profile's `fs`, `subprocess`, `tools`, and `systemPrompt` services and the shared Cordis instance. Installing this package does not install the harness itself.
22
22
 
23
- The bundled DSH LSP service and tool are pinned to `0.1.7-rc.2`. Host peer ranges start at `0.1.7-rc.2` and stop before `0.2.0`. They admit later stable `0.1.x` releases, but semver excludes prereleases of a different patch version. Only `0.1.7-rc.2` is verified here; test each later DSH release before relying on it. Older DSH releases are no longer supported.
23
+ This release pins the DSH LSP service and tool to `0.2.0-rc.1`, matching the required host DSH services. A registry `next` dependency could resolve an older prerelease from cached metadata and cause DSH to reject the installed plugin rows. The repository lockfile and packed-artifact test use the same DSH release.
24
24
 
25
- DSH 0.1.7-rc.2 may stop `plugin add` with `ERR_PNPM_IGNORED_BUILDS` for `core-js`, a dependency of the bundled HTML/CSS server. Decide whether to allow its build script in DSH's plugin manager. To **deny** the script from the CLI, set `allowBuilds.core-js: false` in the selected profile's `pnpm-workspace.yaml` before adding this bundle:
25
+ DSH may stop `plugin add` with `ERR_PNPM_IGNORED_BUILDS` for `core-js`, a dependency of the bundled HTML/CSS server. Decide whether to allow its build script in DSH's plugin manager. To **deny** the script from the CLI, set `allowBuilds.core-js: false` in the selected profile's `pnpm-workspace.yaml` before adding this bundle:
26
26
 
27
27
  ```yaml
28
28
  allowBuilds:
29
29
  core-js: false
30
30
  ```
31
31
 
32
- The packed-artifact test runs HTML/CSS servers with dependency scripts disabled. If an earlier CLI add stopped after writing the dependency, check that `@askdkc/dsh-lsp-server` appears in `dsh.profile.bundles` in that profile's `package.json`; a dependency entry alone does not activate the bundle. If it is absent, remove the package with `dsh plugin --profile web remove @askdkc/dsh-lsp-server`, set the build decision, then repeat the original add command. Use the same launcher prefix you use for `dsh web` (for example, `npx @deepseek-ai/dsh@0.1.7-rc.2` or `pnpm dsh` from a source checkout).
32
+ The packed-artifact test runs HTML/CSS servers with dependency scripts disabled. If an earlier CLI add stopped after writing the dependency, check that `@askdkc/dsh-lsp-server` appears in `dsh.profile.bundles` in that profile's `package.json`; a dependency entry alone does not activate the bundle. If it is absent, remove the package with `dsh plugin --profile web remove @askdkc/dsh-lsp-server`, set the build decision, then repeat the original add command. Use the same launcher prefix you use for `dsh web`.
33
33
 
34
34
  If you already enabled another LSP provider for these extensions, remove its overlapping mappings first: DSH intentionally rejects duplicate ownership with `LSP_CONFLICT`. If your profile already declares the `lsp` or `tool-lsp` rows, compose the provider and extra-tool rows manually instead of inserting the whole bundle twice.
35
35
 
36
- These instructions follow [DSH's profile composition and bundle dependency resolution](https://github.com/deepseek-ai/deepseek-harness/blob/dsh-v0.1.7-rc.2/docs/user/develop/basic/publish.md). No user profile is changed by this repository's tests or doctor command.
36
+ These instructions follow [DSH's profile composition and bundle dependency resolution](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/user/develop/basic/publish.md). No user profile is changed by this repository's tests or doctor command.
37
37
 
38
38
  ## Tools
39
39
 
@@ -104,7 +104,7 @@ PHPANTOM_E2E=1 pnpm test:e2e # additionally tests installed PHPantom with PHP an
104
104
 
105
105
  The packed-artifact test installs the archive into a fresh consumer with DSH's hoisted layout, peer auto-installation disabled, and dependency scripts disabled. It provides the host service packages but does not preinstall either LSP package, then verifies bundle imports, both tool registrations, and real TypeScript, HTML, and CSS queries. It also checks declaration paths and the executable doctor. The consumer install prefers cached packages but needs registry access for uncached packages or metadata. E2E needs working OS file watchers; sandboxed macOS watchers may fail with `EMFILE`.
106
106
 
107
- Integration tests run against the published DSH `0.1.7-rc.2` service/tool packages and Cordis 4.0.4. The full Web UI and a source-built upstream application are not exercised here.
107
+ Integration tests run against the published DSH service/tool packages and Cordis versions recorded in the lockfile. The full Web UI and a source-built upstream application are not exercised here.
108
108
 
109
109
  ### Dependency security
110
110
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@askdkc/dsh-lsp-server",
3
- "version": "0.1.5",
3
+ "version": "0.1.8",
4
4
  "description": "Composite read-only LSP provider for DeepSeek Harness web stacks",
5
5
  "type": "module",
6
6
  "main": "./lib/provider.js",
@@ -47,8 +47,8 @@
47
47
  "prepublishOnly": "npm run check"
48
48
  },
49
49
  "dependencies": {
50
- "@deepseek-ai/dsh-lsp": "0.1.7-rc.2",
51
- "@deepseek-ai/dsh-tool-lsp": "0.1.7-rc.2",
50
+ "@deepseek-ai/dsh-lsp": "0.2.0-rc.1",
51
+ "@deepseek-ai/dsh-tool-lsp": "0.2.0-rc.1",
52
52
  "@tailwindcss/language-server": "0.16.0",
53
53
  "svelte-language-server": "0.17.15",
54
54
  "typescript": "5.7.3",
@@ -57,43 +57,43 @@
57
57
  },
58
58
  "peerDependencies": {
59
59
  "@deepseek-ai/cordis": "~4.0.4",
60
- "@deepseek-ai/dsh-fs": ">=0.1.7-rc.2 <0.2.0",
61
- "@deepseek-ai/dsh-subprocess": ">=0.1.7-rc.2 <0.2.0",
62
- "@deepseek-ai/dsh-system-prompt": ">=0.1.7-rc.2 <0.2.0",
63
- "@deepseek-ai/dsh-tools": ">=0.1.7-rc.2 <0.2.0",
60
+ "@deepseek-ai/dsh-fs": "0.2.0-rc.1",
61
+ "@deepseek-ai/dsh-subprocess": "0.2.0-rc.1",
62
+ "@deepseek-ai/dsh-system-prompt": "0.2.0-rc.1",
63
+ "@deepseek-ai/dsh-tools": "0.2.0-rc.1",
64
64
  "@deepseek-ai/schemastery": "~3.18.4"
65
65
  },
66
66
  "devDependencies": {
67
67
  "@deepseek-ai/cordis": "~4.0.4",
68
- "@deepseek-ai/dsh-agent": "0.1.7-rc.2",
69
- "@deepseek-ai/dsh-brand": "0.1.7-rc.2",
70
- "@deepseek-ai/dsh-fs": "0.1.7-rc.2",
71
- "@deepseek-ai/dsh-fs-local": "0.1.7-rc.2",
72
- "@deepseek-ai/dsh-http-proxy": "0.1.7-rc.2",
73
- "@deepseek-ai/dsh-invariants": "0.1.7-rc.2",
74
- "@deepseek-ai/dsh-llm": "0.1.7-rc.2",
75
- "@deepseek-ai/dsh-ptc-runtime": "0.1.7-rc.2",
76
- "@deepseek-ai/dsh-sandbox": "0.1.7-rc.2",
77
- "@deepseek-ai/dsh-sandbox-policy": "0.1.7-rc.2",
78
- "@deepseek-ai/dsh-scope": "0.1.7-rc.2",
79
- "@deepseek-ai/dsh-session": "0.1.7-rc.2",
80
- "@deepseek-ai/dsh-session-projection": "0.1.7-rc.2",
81
- "@deepseek-ai/dsh-subprocess": "0.1.7-rc.2",
82
- "@deepseek-ai/dsh-subprocess-local": "0.1.7-rc.2",
83
- "@deepseek-ai/dsh-system-prompt": "0.1.7-rc.2",
84
- "@deepseek-ai/dsh-timeout": "0.1.7-rc.2",
85
- "@deepseek-ai/dsh-tools": "0.1.7-rc.2",
86
- "@deepseek-ai/dsh-user-approval": "0.1.7-rc.2",
68
+ "@deepseek-ai/dsh-agent": "0.2.0-rc.1",
69
+ "@deepseek-ai/dsh-brand": "0.2.0-rc.1",
70
+ "@deepseek-ai/dsh-fs": "0.2.0-rc.1",
71
+ "@deepseek-ai/dsh-fs-local": "0.2.0-rc.1",
72
+ "@deepseek-ai/dsh-http-proxy": "0.2.0-rc.1",
73
+ "@deepseek-ai/dsh-invariants": "0.2.0-rc.1",
74
+ "@deepseek-ai/dsh-llm": "0.2.0-rc.1",
75
+ "@deepseek-ai/dsh-ptc-runtime": "0.2.0-rc.1",
76
+ "@deepseek-ai/dsh-sandbox": "0.2.0-rc.1",
77
+ "@deepseek-ai/dsh-sandbox-policy": "0.2.0-rc.1",
78
+ "@deepseek-ai/dsh-scope": "0.2.0-rc.1",
79
+ "@deepseek-ai/dsh-session": "0.2.0-rc.1",
80
+ "@deepseek-ai/dsh-session-projection": "0.2.0-rc.1",
81
+ "@deepseek-ai/dsh-subprocess": "0.2.0-rc.1",
82
+ "@deepseek-ai/dsh-subprocess-local": "0.2.0-rc.1",
83
+ "@deepseek-ai/dsh-system-prompt": "0.2.0-rc.1",
84
+ "@deepseek-ai/dsh-timeout": "0.2.0-rc.1",
85
+ "@deepseek-ai/dsh-tools": "0.2.0-rc.1",
86
+ "@deepseek-ai/dsh-user-approval": "0.2.0-rc.1",
87
87
  "@deepseek-ai/schemastery": "~3.18.4",
88
88
  "@types/node": "22.10.5",
89
89
  "tailwindcss-v3": "npm:tailwindcss@3.4.17",
90
90
  "tailwindcss-v4": "npm:tailwindcss@4.1.13",
91
91
  "tsdown": "0.15.0",
92
92
  "typescript": "5.7.3",
93
- "vitest": "3.2.6"
93
+ "vitest": "4.1.11"
94
94
  },
95
95
  "engines": {
96
- "node": ">=22.18.0"
96
+ "node": "^22.19.0 || >=24.0.0"
97
97
  },
98
98
  "publishConfig": {
99
99
  "access": "public"