@crawlee/fs-storage 4.0.0-beta.100

package/LICENSE.md

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "{}"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2018 Apify Technologies s.r.o.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,153 @@
+<h1 align="center">
+    <a href="https://crawlee.dev">
+        <picture>
+          <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/apify/crawlee/master/website/static/img/crawlee-dark.svg?sanitize=true" />
+          <img alt="Crawlee" src="https://raw.githubusercontent.com/apify/crawlee/master/website/static/img/crawlee-light.svg?sanitize=true" width="500" />
+        </picture>
+    </a>
+    <br />
+    <small>A web scraping and browser automation library</small>
+</h1>
+
+<p align="center">
+    <a href="https://trendshift.io/repositories/5179" target="_blank"><img src="https://trendshift.io/api/badge/repositories/5179" alt="apify%2Fcrawlee | Trendshift" width="250" height="55"/></a>
+</p>
+
+<p align="center">
+    <a href="https://www.npmjs.com/package/@crawlee/core" rel="nofollow"><img src="https://img.shields.io/npm/v/@crawlee/core.svg" alt="NPM latest version" data-canonical-src="https://img.shields.io/npm/v/@crawlee/core/next.svg" /></a>
+    <a href="https://www.npmjs.com/package/@crawlee/core" rel="nofollow"><img src="https://img.shields.io/npm/dm/@crawlee/core.svg" alt="Downloads" data-canonical-src="https://img.shields.io/npm/dm/@crawlee/core.svg" /></a>
+    <a href="https://discord.gg/jyEM2PRvMU" rel="nofollow"><img src="https://img.shields.io/discord/801163717915574323?label=discord" alt="Chat on discord" data-canonical-src="https://img.shields.io/discord/801163717915574323?label=discord" /></a>
+    <a href="https://github.com/apify/crawlee/actions/workflows/test-ci.yml"><img src="https://github.com/apify/crawlee/actions/workflows/test-ci.yml/badge.svg?branch=master" alt="Build Status" /></a>
+</p>
+
+Crawlee covers your crawling and scraping end-to-end and **helps you build reliable scrapers. Fast.**
+
+Your crawlers will appear human-like and fly under the radar of modern bot protections even with the default configuration. Crawlee gives you the tools to crawl the web for links, scrape data, and store it to disk or cloud while staying configurable to suit your project's needs.
+
+Crawlee is available as the [`crawlee`](https://www.npmjs.com/package/crawlee) NPM package.
+
+> 👉 **View full documentation, guides and examples on the [Crawlee project website](https://crawlee.dev)** 👈
+
+> Do you prefer 🐍 Python instead of JavaScript? [👉 Checkout Crawlee for Python 👈](https://github.com/apify/crawlee-python).
+
+## Installation
+
+We recommend visiting the [Introduction tutorial](https://crawlee.dev/js/docs/introduction) in Crawlee documentation for more information.
+
+> Crawlee requires **Node.js 16 or higher**.
+
+### With Crawlee CLI
+
+The fastest way to try Crawlee out is to use the **Crawlee CLI** and choose the **Getting started example**. The CLI will install all the necessary dependencies and add boilerplate code for you to play with.
+
+```bash
+npx crawlee create my-crawler
+```
+
+```bash
+cd my-crawler
+npm start
+```
+
+### Manual installation
+If you prefer adding Crawlee **into your own project**, try the example below. Because it uses `PlaywrightCrawler` we also need to install [Playwright](https://playwright.dev). It's not bundled with Crawlee to reduce install size.
+
+```bash
+npm install crawlee playwright
+```
+
+```js
+import { PlaywrightCrawler, Dataset } from 'crawlee';
+
+// PlaywrightCrawler crawls the web using a headless
+// browser controlled by the Playwright library.
+const crawler = new PlaywrightCrawler({
+    // Use the requestHandler to process each of the crawled pages.
+    async requestHandler({ request, page, enqueueLinks, log }) {
+        const title = await page.title();
+        log.info(`Title of ${request.loadedUrl} is '${title}'`);
+
+        // Save results as JSON to ./storage/datasets/default
+        await Dataset.pushData({ title, url: request.loadedUrl });
+
+        // Extract links from the current page
+        // and add them to the crawling queue.
+        await enqueueLinks();
+    },
+    // Uncomment this option to see the browser window.
+    // headless: false,
+});
+
+// Add first URL to the queue and start the crawl.
+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/js/docs/guides/configuration), [Request storage](https://crawlee.dev/js/docs/guides/request-storage) and [Result storage](https://crawlee.dev/js/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 crawlee@next
+```
+
+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": "$crawlee",
+           "@crawlee/types": "$crawlee",
+           "@crawlee/utils": "$crawlee"
+       }
+    }
+}
+```
+
+## 🛠 Features
+
+- Single interface for **HTTP and headless browser** crawling
+- Persistent **queue** for URLs to crawl (breadth & depth first)
+- Pluggable **storage** of both tabular data and files
+- Automatic **scaling** with available system resources
+- Integrated **proxy rotation** and session management
+- Lifecycles customizable with **hooks**
+- **CLI** to bootstrap your projects
+- Configurable **routing**, **error handling** and **retries**
+- **Dockerfiles** ready to deploy
+- Written in **TypeScript** with generics
+
+### 👾 HTTP crawling
+
+- Zero config **HTTP2 support**, even for proxies
+- Automatic generation of **browser-like headers**
+- Replication of browser **TLS fingerprints**
+- Integrated fast **HTML parsers**. Cheerio and JSDOM
+- Yes, you can scrape **JSON APIs** as well
+
+### 💻 Real browser crawling
+
+- JavaScript **rendering** and **screenshots**
+- **Headless** and **headful** support
+- Zero-config generation of **human-like fingerprints**
+- Automatic **browser management**
+- Use **Playwright** and **Puppeteer** with the same interface
+- **Chrome**, **Firefox**, **Webkit** and many others
+
+## Usage on the Apify platform
+
+Crawlee is open-source and runs anywhere, but since it's developed by [Apify](https://apify.com), it's easy to set up on the Apify platform and run in the cloud. Visit the [Apify SDK website](https://sdk.apify.com) to learn more about deploying Crawlee to the Apify platform.
+
+## Support
+
+If you find any bug or issue with Crawlee, please [submit an issue on GitHub](https://github.com/apify/crawlee/issues). For questions, you can ask on [Stack Overflow](https://stackoverflow.com/questions/tagged/apify), in GitHub Discussions or you can join our [Discord server](https://discord.com/invite/jyEM2PRvMU).
+
+## Contributing
+
+Your code contributions are welcome, and you'll be praised to eternity! If you have any ideas for improvements, either submit an issue or create a pull request. For contribution guidelines and the code of conduct, see [CONTRIBUTING.md](https://github.com/apify/crawlee/blob/master/CONTRIBUTING.md).
+
+## License
+
+This project is licensed under the Apache License 2.0 - see the [LICENSE.md](https://github.com/apify/crawlee/blob/master/LICENSE.md) file for details.

package/file-system-storage.d.ts

@@ -0,0 +1,87 @@
+import type * as storage from '@crawlee/types';
+import type { CrawleeLogger } from '@crawlee/types';
+import { DatasetBackend } from './resource-clients/dataset.js';
+import { KeyValueStoreBackend } from './resource-clients/key-value-store.js';
+import { RequestQueueBackend } from './resource-clients/request-queue.js';
+export interface FileSystemStorageOptions {
+    /**
+     * Path to directory where the data will be saved.
+     */
+    localDataDirectory: string;
+    /**
+     * Optional logger for FileSystemStorageBackend warnings.
+     */
+    logger?: CrawleeLogger;
+    /**
+     * How the on-disk request queues opened by this backend are expected to be accessed.
+     *
+     * With `'single'` (the default), this process asserts it is the *sole* consumer of every request
+     * queue it opens: on open, any requests that a previous run left *in progress* (e.g. after a
+     * crash) are reclaimed immediately, so they become fetchable again right away. This is the right
+     * behavior for the common single-process crawl.
+     *
+     * Use `'shared'` if multiple processes share the same on-disk request queue concurrently (for
+     * example, the {@link parallel scraping setup | "Parallel Scraping Guide"}). In that mode an
+     * in-progress request is treated as a potential live peer's lock and is only reclaimed once that
+     * lock expires on the wall clock, so two workers won't process the same request at once.
+     *
+     * @default 'single'
+     */
+    requestQueueAccess?: 'single' | 'shared';
+}
+/**
+ * A file-system storage backend backed by the native `@crawlee/fs-storage-native` Rust extension.
+ *
+ * The native extension owns the on-disk format, timestamps, item counting, request-queue locking and
+ * state persistence. This class is responsible for resolving the user-facing `id` / `name` / `alias`
+ * identifiers to native storages, caching the opened backends (so that `storageExists`, `purge` and
+ * `teardown` can operate over them), and exposing them through the `@crawlee/types` interfaces.
+ */
+export declare class FileSystemStorageBackend implements storage.StorageBackend {
+    readonly localDataDirectory: string;
+    readonly datasetsDirectory: string;
+    readonly keyValueStoresDirectory: string;
+    readonly requestQueuesDirectory: string;
+    readonly logger?: CrawleeLogger;
+    readonly requestQueueAccess: 'single' | 'shared';
+    readonly keyValueStoreBackendCache: KeyValueStoreBackend[];
+    readonly datasetBackendCache: DatasetBackend[];
+    readonly requestQueueBackendCache: RequestQueueBackend[];
+    constructor(options: FileSystemStorageOptions);
+    /**
+     * Return a cache key that includes the resolved storage directory, so that two
+     * `FileSystemStorageBackend` instances pointing at different directories get separate cache
+     * partitions, by including the storage directory in the cache key.
+     */
+    getStorageBackendCacheKey(): string;
+    private static resolveStorageKey;
+    createDatasetBackend(options?: storage.StorageIdentifier): Promise<storage.DatasetBackend>;
+    createKeyValueStoreBackend(options?: storage.StorageIdentifier): Promise<storage.KeyValueStoreBackend>;
+    createRequestQueueBackend(options?: storage.StorageIdentifier): Promise<storage.RequestQueueBackend>;
+    storageExists(id: string, type: 'Dataset' | 'KeyValueStore' | 'RequestQueue'): Promise<boolean>;
+    /**
+     * Resolve the real `id` of the on-disk storage identified by `entryNameOrId` under `baseDirectory`,
+     * or `undefined` if none matches. The storage's real id lives in its directory's
+     * `__metadata__.json`; the directory itself is named after the storage's `name ?? id`. So this
+     * first tries the directory named exactly `entryNameOrId` (reading its metadata id), then falls
+     * back to scanning sibling directories for one whose metadata id equals `entryNameOrId` (the case
+     * of a storage opened by name and later looked up by its auto-assigned id).
+     */
+    private static resolveStorageIdOnDisk;
+    /** Read the `id` field from a storage directory's `__metadata__.json`, or `undefined` if absent. */
+    private static readMetadataId;
+    /**
+     * Cleans up the default storages before the run starts:
+     *  - the default dataset;
+     *  - all records from the default key-value store, except for the "INPUT" key;
+     *  - the default request queue.
+     */
+    purge(): Promise<void>;
+    /**
+     * This method should be called at the end of the process, to ensure all data is saved.
+     *
+     * It persists the state of every opened request queue so that requests fetched but not yet handled
+     * are not stuck (until their lock expires) for the next consumer of the same on-disk queue.
+     */
+    teardown(): Promise<void>;
+}

package/file-system-storage.js

@@ -0,0 +1,229 @@
+import { opendir, readFile } from 'node:fs/promises';
+import { resolve } from 'node:path';
+import { s } from '@sapphire/shapeshift';
+import { FileSystemDatasetClient as NativeDatasetBackend, FileSystemKeyValueStoreClient as NativeKeyValueStoreBackend, FileSystemRequestQueueClient as NativeRequestQueueBackend, } from '@crawlee/fs-storage-native';
+import { DatasetBackend } from './resource-clients/dataset.js';
+import { KeyValueStoreBackend } from './resource-clients/key-value-store.js';
+import { RequestQueueBackend } from './resource-clients/request-queue.js';
+/**
+ * A file-system storage backend backed by the native `@crawlee/fs-storage-native` Rust extension.
+ *
+ * The native extension owns the on-disk format, timestamps, item counting, request-queue locking and
+ * state persistence. This class is responsible for resolving the user-facing `id` / `name` / `alias`
+ * identifiers to native storages, caching the opened backends (so that `storageExists`, `purge` and
+ * `teardown` can operate over them), and exposing them through the `@crawlee/types` interfaces.
+ */
+export class FileSystemStorageBackend {
+    localDataDirectory;
+    datasetsDirectory;
+    keyValueStoresDirectory;
+    requestQueuesDirectory;
+    logger;
+    requestQueueAccess;
+    keyValueStoreBackendCache = [];
+    datasetBackendCache = [];
+    requestQueueBackendCache = [];
+    constructor(options) {
+        s.object({
+            localDataDirectory: s.string(),
+            requestQueueAccess: s.enum(['single', 'shared']).optional(),
+        }).parse(options);
+        this.logger = options.logger;
+        this.requestQueueAccess = options.requestQueueAccess ?? 'single';
+        this.localDataDirectory = options.localDataDirectory;
+        this.datasetsDirectory = resolve(this.localDataDirectory, 'datasets');
+        this.keyValueStoresDirectory = resolve(this.localDataDirectory, 'key_value_stores');
+        this.requestQueuesDirectory = resolve(this.localDataDirectory, 'request_queues');
+    }
+    /**
+     * Return a cache key that includes the resolved storage directory, so that two
+     * `FileSystemStorageBackend` instances pointing at different directories get separate cache
+     * partitions, by including the storage directory in the cache key.
+     */
+    getStorageBackendCacheKey() {
+        return `FileSystemStorageBackend:${resolve(this.localDataDirectory)}`;
+    }
+    static resolveStorageKey(options) {
+        const isAlias = 'alias' in options && !!options.alias;
+        const rawKey = isAlias ? options.alias : (options.name ?? options.id);
+        // Normalize the internal __default__ alias to the user-facing 'default' name.
+        const cacheKey = rawKey === '__default__' ? 'default' : rawKey;
+        return { id: options.id, name: options.name, alias: options.alias, cacheKey };
+    }
+    async createDatasetBackend(options = {}) {
+        const { id, name, alias, cacheKey } = FileSystemStorageBackend.resolveStorageKey(options);
+        if (cacheKey) {
+            const found = this.datasetBackendCache.find((store) => store.id === cacheKey ||
+                store.name?.toLowerCase() === cacheKey.toLowerCase() ||
+                store.cacheKey.toLowerCase() === cacheKey.toLowerCase());
+            if (found) {
+                return found;
+            }
+        }
+        const nativeBackend = await NativeDatasetBackend.open(id, name, alias, this.localDataDirectory);
+        const newStore = await DatasetBackend.create({
+            name: alias ? undefined : (name ?? cacheKey),
+            cacheKey: cacheKey ?? '',
+            nativeBackend,
+            logger: this.logger,
+        });
+        this.datasetBackendCache.push(newStore);
+        return newStore;
+    }
+    async createKeyValueStoreBackend(options = {}) {
+        const { id, name, alias, cacheKey } = FileSystemStorageBackend.resolveStorageKey(options);
+        if (cacheKey) {
+            const found = this.keyValueStoreBackendCache.find((store) => store.id === cacheKey ||
+                store.name?.toLowerCase() === cacheKey.toLowerCase() ||
+                store.cacheKey.toLowerCase() === cacheKey.toLowerCase());
+            if (found) {
+                return found;
+            }
+        }
+        const nativeBackend = await NativeKeyValueStoreBackend.open(id, name, alias, this.localDataDirectory);
+        const newStore = await KeyValueStoreBackend.create({
+            name: alias ? undefined : (name ?? cacheKey),
+            cacheKey: cacheKey ?? '',
+            nativeBackend,
+            logger: this.logger,
+        });
+        this.keyValueStoreBackendCache.push(newStore);
+        return newStore;
+    }
+    async createRequestQueueBackend(options = {}) {
+        const { id, name, alias, cacheKey } = FileSystemStorageBackend.resolveStorageKey(options);
+        if (cacheKey) {
+            const found = this.requestQueueBackendCache.find((queue) => queue.id === cacheKey ||
+                queue.name?.toLowerCase() === cacheKey.toLowerCase() ||
+                queue.cacheKey.toLowerCase() === cacheKey.toLowerCase());
+            if (found) {
+                return found;
+            }
+        }
+        const nativeBackend = await NativeRequestQueueBackend.open(id, name, alias, this.localDataDirectory, 
+        // useTestClock — always real wall-clock outside of native tests.
+        undefined, this.requestQueueAccess);
+        const newStore = await RequestQueueBackend.create({
+            name: alias ? undefined : (name ?? cacheKey),
+            cacheKey: cacheKey ?? '',
+            nativeBackend,
+            logger: this.logger,
+        });
+        this.requestQueueBackendCache.push(newStore);
+        return newStore;
+    }
+    async storageExists(id, type) {
+        let backends;
+        let baseDir;
+        switch (type) {
+            case 'Dataset':
+                backends = this.datasetBackendCache;
+                baseDir = this.datasetsDirectory;
+                break;
+            case 'KeyValueStore':
+                backends = this.keyValueStoreBackendCache;
+                baseDir = this.keyValueStoresDirectory;
+                break;
+            case 'RequestQueue':
+                backends = this.requestQueueBackendCache;
+                baseDir = this.requestQueuesDirectory;
+                break;
+            default:
+                return false;
+        }
+        // Check the in-memory cache by actual storage ID first.
+        if (backends.some((store) => store.id === id)) {
+            return true;
+        }
+        // Otherwise, resolve any on-disk storage that matches the queried string — either by its
+        // directory name, or (for a storage opened by name, whose directory is named after the name)
+        // by scanning the `__metadata__.json` files for a matching id.
+        //
+        // A directory-name match does NOT by itself prove the string is the storage's *id*: the
+        // directory is named after `name ?? id`, so `named-storage`/`on-disk` (a name or alias) also
+        // has a matching directory. We therefore read the real id from the metadata and only report
+        // existence when it equals the queried string. This matches upstream PR #3800/#3808 and
+        // prevents a named storage from being re-resolved as `{ id: name }` on a subsequent run.
+        const resolvedId = await FileSystemStorageBackend.resolveStorageIdOnDisk(baseDir, id);
+        return resolvedId === id;
+    }
+    /**
+     * Resolve the real `id` of the on-disk storage identified by `entryNameOrId` under `baseDirectory`,
+     * or `undefined` if none matches. The storage's real id lives in its directory's
+     * `__metadata__.json`; the directory itself is named after the storage's `name ?? id`. So this
+     * first tries the directory named exactly `entryNameOrId` (reading its metadata id), then falls
+     * back to scanning sibling directories for one whose metadata id equals `entryNameOrId` (the case
+     * of a storage opened by name and later looked up by its auto-assigned id).
+     */
+    static async resolveStorageIdOnDisk(baseDirectory, entryNameOrId) {
+        // Directory named exactly after the string: return its real (metadata) id, which may differ
+        // from the string when the string is a name rather than an id.
+        const directId = await FileSystemStorageBackend.readMetadataId(resolve(baseDirectory, entryNameOrId));
+        if (directId !== undefined) {
+            return directId;
+        }
+        // No such directory — scan siblings for one whose metadata id matches the string.
+        let directories;
+        try {
+            directories = await opendir(baseDirectory);
+        }
+        catch {
+            return undefined;
+        }
+        for await (const directory of directories) {
+            if (!directory.isDirectory()) {
+                continue;
+            }
+            const metadataId = await FileSystemStorageBackend.readMetadataId(resolve(baseDirectory, directory.name));
+            if (metadataId === entryNameOrId) {
+                return metadataId;
+            }
+        }
+        return undefined;
+    }
+    /** Read the `id` field from a storage directory's `__metadata__.json`, or `undefined` if absent. */
+    static async readMetadataId(storageDirectory) {
+        try {
+            const fileContent = await readFile(resolve(storageDirectory, '__metadata__.json'), 'utf8');
+            return JSON.parse(fileContent).id;
+        }
+        catch {
+            // Directory missing, or no/unreadable metadata file — no id to report.
+            return undefined;
+        }
+    }
+    /**
+     * Cleans up the default storages before the run starts:
+     *  - the default dataset;
+     *  - all records from the default key-value store, except for the "INPUT" key;
+     *  - the default request queue.
+     */
+    async purge() {
+        // Resolve the default stores up front so leftover on-disk records are purged even when the
+        // store has not been opened in this process yet (e.g. a fresh run over a pre-existing
+        // directory). Opening caches the backend, so the subsequent purge operates on a real backend.
+        // The default store is opened via the internal `__default__` alias (see resolveStorageIdentifier
+        // in @crawlee/core), which resolves to the `default` cache key — match that here so we purge the
+        // very backend the default open would return rather than creating a divergent one.
+        const [defaultKeyValueStore, defaultDataset, defaultRequestQueue] = await Promise.all([
+            this.createKeyValueStoreBackend({ alias: '__default__' }),
+            this.createDatasetBackend({ alias: '__default__' }),
+            this.createRequestQueueBackend({ alias: '__default__' }),
+        ]);
+        await Promise.all([
+            // Preserve the run input (INPUT) when purging the default key-value store.
+            defaultKeyValueStore.purgeExceptInput(),
+            defaultDataset.purge(),
+            defaultRequestQueue.purge(),
+        ]);
+    }
+    /**
+     * This method should be called at the end of the process, to ensure all data is saved.
+     *
+     * It persists the state of every opened request queue so that requests fetched but not yet handled
+     * are not stuck (until their lock expires) for the next consumer of the same on-disk queue.
+     */
+    async teardown() {
+        await Promise.all(this.requestQueueBackendCache.map(async (queue) => queue.persistState()));
+    }
+}