@onecrew/pro 0.1.18-win-test.2 → 0.1.18-win-test.3

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 (2) hide show
  1. package/README.md +12 -10
  2. package/package.json +21 -12
package/README.md CHANGED
@@ -1,16 +1,18 @@
1
1
  # OneCrew Pro
2
2
 
3
- Windows x64 preview of the application updater. The application reports version 0.1.18. The npm entry and Windows platform package use version 0.1.18-win-test.2.
3
+ Install Node.js with npm, then run:
4
4
 
5
- Install with Node.js 20 or newer:
6
-
7
- ```powershell
8
- npm.cmd install --global "@onecrew/pro@0.1.18-win-test.2" --registry=https://registry.npmjs.org/ --include=optional --ignore-scripts
9
- onecrew-pro.cmd --print-binary-path
10
- onecrew-pro.cmd start
11
- onecrew-pro.cmd status
5
+ ```sh
6
+ npm install --global @onecrew/pro@0.1.18-win-test.3 --registry=https://registry.npmjs.org/
7
+ onecrew-pro --version
8
+ onecrew-pro start
9
+ onecrew-pro status
12
10
  ```
13
11
 
14
- Use `onecrew-pro.cmd stop` to stop the service. The npm entry supports `--print-binary-path`; pass the returned native executable and `mcp` arguments to MCP clients. Preserve the service's data directory when updating or connecting a client.
12
+ The service uses the existing OneCrewConnect data directory. Complete sign-in in the local URL printed by start/status.
13
+
14
+ Before updating, run `onecrew-pro stop` for the profile in use, install the new package version, then run `onecrew-pro start`. For an existing ZIP installation, stop its installed binary before installing the npm package. Keep its data directory.
15
+
16
+ MCP clients can run `onecrew-pro mcp`. The service must already be running. `onecrew-pro --print-binary-path` returns the absolute native executable path for clients that need one. Keep optional dependencies enabled so npm can install the platform binary.
15
17
 
16
- This preview uses the normal application commands and data directory. The stable npm `latest` tag remains unchanged. Application updates are available when Access publishes a newer application version.
18
+ Connect the AI client you use by following the [macOS npm guide](https://access.onecrewai.io/cli/install/pro/npm) or [Windows npm guide](https://access.onecrewai.io/cli/install/pro/npm/windows). Access provides the client-specific configuration and verification steps.
package/package.json CHANGED
@@ -1,20 +1,29 @@
1
1
  {
2
2
  "name": "@onecrew/pro",
3
- "version": "0.1.18-win-test.2",
4
- "description": "OneCrew Pro local service and MCP bridge",
3
+ "version": "0.1.18-win-test.3",
5
4
  "license": "MIT",
6
5
  "homepage": "https://onecrewai.io",
7
- "engines": {"node": ">=20"},
8
- "os": ["win32"],
9
- "cpu": ["x64"],
10
- "bin": {"onecrew-pro": "bin/onecrew-pro.cjs"},
11
- "files": ["bin/"],
12
- "optionalDependencies": {
13
- "@onecrew/pro-win32-x64": "0.1.18-win-test.2"
14
- },
15
6
  "publishConfig": {
16
7
  "access": "public",
17
- "registry": "https://registry.npmjs.org/",
18
- "tag": "win-test"
8
+ "registry": "https://registry.npmjs.org/"
9
+ },
10
+ "description": "OneCrew Pro local service and MCP bridge",
11
+ "engines": {
12
+ "node": ">=20"
13
+ },
14
+ "os": [
15
+ "win32"
16
+ ],
17
+ "cpu": [
18
+ "x64"
19
+ ],
20
+ "bin": {
21
+ "onecrew-pro": "bin/onecrew-pro.cjs"
22
+ },
23
+ "files": [
24
+ "bin/"
25
+ ],
26
+ "optionalDependencies": {
27
+ "@onecrew/pro-win32-x64": "0.1.18-win-test.3"
19
28
  }
20
29
  }