@dbalabka/chrome-wsl 0.2.0 → 0.2.2
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.
- package/README.md +5 -28
- package/package.json +4 -5
package/README.md
CHANGED
|
@@ -17,41 +17,18 @@ A small WSL helper to open Google Chrome on Windows with remote debugging (port
|
|
|
17
17
|
- Windows Chrome installed at `C:\Program Files\Google\Chrome\Application\chrome.exe` (adjust the path in the script if different).
|
|
18
18
|
- Network/apt access to install `socat` on first run (or preinstall manually).
|
|
19
19
|
|
|
20
|
-
## Usage
|
|
20
|
+
## Usage (npx)
|
|
21
21
|
```sh
|
|
22
|
-
|
|
22
|
+
npx @dbalabka/chrome-wsl
|
|
23
23
|
```
|
|
24
24
|
- If portproxy/firewall entries are missing, run the printed admin PowerShell commands on Windows, then rerun the script.
|
|
25
25
|
- The script logs `socat` output to `/tmp/socat-9222.log`.
|
|
26
26
|
- To stop the `socat` forwarder:
|
|
27
27
|
```sh
|
|
28
|
-
|
|
29
|
-
```
|
|
30
|
-
|
|
31
|
-
## Installation (one-liner)
|
|
32
|
-
```sh
|
|
33
|
-
sudo install -m 755 chrome-wsl.sh /usr/local/bin/start-chrome-wsl
|
|
34
|
-
```
|
|
35
|
-
- Uses the local script (no curl/wget download needed). If you cloned the repo elsewhere, run from that path.
|
|
36
|
-
- Adjust `WINDOWS_CHROME_PATH` or `PORT` inside the script if needed.
|
|
37
|
-
- If `apt` is blocked, preinstall `socat` via your allowed package source.
|
|
38
|
-
|
|
39
|
-
## Installation via npx
|
|
40
|
-
```sh
|
|
41
|
-
npx --yes @dbalabka/chrome-wsl start-chrome-wsl
|
|
42
|
-
```
|
|
43
|
-
- Runs directly via npm without cloning; explicitly invokes the `start-chrome-wsl` binary from the scoped package.
|
|
44
|
-
- Use `npm install -g start-chrome-wsl` to keep it available without npx.
|
|
45
|
-
|
|
46
|
-
## Installation via pipx
|
|
47
|
-
```sh
|
|
48
|
-
pipx install start-chrome-wsl
|
|
49
|
-
```
|
|
50
|
-
- Installs the wrapper that invokes the same `start_chrome_wsl.sh` script.
|
|
51
|
-
- Alternatively, run without installing globally:
|
|
52
|
-
```sh
|
|
53
|
-
pipx run start-chrome-wsl --stop
|
|
28
|
+
npx @dbalabka/chrome-wsl -- --stop
|
|
54
29
|
```
|
|
30
|
+
- Runs directly via npm without cloning; default entrypoint is `chrome-wsl` (matching the package name).
|
|
31
|
+
- To install globally instead of npx: `npm install -g @dbalabka/chrome-wsl` then run `chrome-wsl` or `chrome-wsl --stop`.
|
|
55
32
|
|
|
56
33
|
## Notes
|
|
57
34
|
- Portproxy check expects forwarding from the detected Windows host IP to `127.0.0.1:9222`.
|
package/package.json
CHANGED
|
@@ -1,13 +1,12 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@dbalabka/chrome-wsl",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.2",
|
|
4
4
|
"description": "WSL helper to start Windows Chrome with remote debugging and socat port forwarding.",
|
|
5
|
-
"bin":
|
|
6
|
-
"chrome-wsl": "chrome-wsl.sh"
|
|
7
|
-
},
|
|
5
|
+
"bin": "chrome-wsl.sh",
|
|
8
6
|
"files": [
|
|
9
7
|
"chrome-wsl.sh",
|
|
10
|
-
"README.md"
|
|
8
|
+
"README.md",
|
|
9
|
+
"LICENSE"
|
|
11
10
|
],
|
|
12
11
|
"keywords": [
|
|
13
12
|
"wsl",
|