You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+16-2Lines changed: 16 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,12 +55,12 @@ $ cd browser-use-node
55
55
# With yarn
56
56
$ yarn link
57
57
$ cd ../my-package
58
-
$ yarn link browser-use-node
58
+
$ yarn link browser-use-sdk
59
59
60
60
# With pnpm
61
61
$ pnpm link --global
62
62
$ cd ../my-package
63
-
$ pnpm link -—global browser-use-node
63
+
$ pnpm link -—global browser-use-sdk
64
64
```
65
65
66
66
## Running tests
@@ -91,3 +91,17 @@ To format and fix all lint issues automatically:
91
91
```sh
92
92
$ yarn fix
93
93
```
94
+
95
+
## Publishing and releases
96
+
97
+
Changes made to this repository via the automated release PR pipeline should publish to npm automatically. If
98
+
the changes aren't made through the automated pipeline, you may want to make releases manually.
99
+
100
+
### Publish with a GitHub workflow
101
+
102
+
You can release to package managers by using [the `Publish NPM` GitHub action](https://www.github.com/browser-use/browser-use-node/actions/workflows/publish-npm.yml). This requires a setup organization or repository secret to be set up.
103
+
104
+
### Publish manually
105
+
106
+
If you need to manually release a package, you can run the `bin/publish-npm` script with an `NPM_TOKEN` set on
If you want to set custom `fetch` options without overriding the `fetch` function, you can provide a `fetchOptions` object when instantiating the client or making a request. (Request-specific options override client options.)
0 commit comments