Skip to content

Commit

Permalink
docs: Mention how to install beta builds (#2850)
Browse files Browse the repository at this point in the history
  • Loading branch information
janbuchar authored Feb 17, 2025
1 parent cfd7e43 commit cbd3946
Showing 1 changed file with 22 additions and 0 deletions.
22 changes: 22 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -80,6 +80,28 @@ await crawler.run(['https://crawlee.dev']);

By default, Crawlee stores data to `./storage` in the current working directory. You can override this directory via Crawlee configuration. For details, see [Configuration guide](https://crawlee.dev/docs/guides/configuration), [Request storage](https://crawlee.dev/docs/guides/request-storage) and [Result storage](https://crawlee.dev/docs/guides/result-storage).

### Installing pre-release versions

We provide automated beta builds for every merged code change in Crawlee. You can find them in the npm [list of releases](https://www.npmjs.com/package/crawlee?activeTab=versions). If you want to test new features or bug fixes before we release them, feel free to install a beta build like this:

```bash
npm install [email protected]
```

If you also use the [Apify SDK](https://github.com/apify/apify-sdk-js), you need to specify dependency overrides in your `package.json` file so that you don't end up with multiple versions of Crawlee installed:

```json
{
"overrides": {
"apify": {
"@crawlee/core": "3.12.3-beta.13",
"@crawlee/types": "3.12.3-beta.13",
"@crawlee/utils": "3.12.3-beta.13"
}
}
}
```

## 🛠 Features

- Single interface for **HTTP and headless browser** crawling
Expand Down

0 comments on commit cbd3946

Please sign in to comment.