Dataset directory still set to "./storage" after configuration set in code

[jo-sip]

Which package is this bug report for? If unsure which one to select, leave blank

@crawlee/core

Issue description

When I run my code, it outputs to ./storage even after I update my storage directory in code. However, the key_value_stores and request_queues respect the new setting.

Code sample

const config = new Configuration({
  purgeOnStart: true,
  persistStateIntervalMillis: 10_000,
  storageClientOptions: {
    localDataDirectory: path.join(__dirname, ".tmp", "crawlee-data"),
  },
});

// Run code

// Writes to ./storage where this code was run. But not for `key_value_stores` and `request_queues`, which are in `.tmp/crawlee-data`.

### Package version

[email protected]

### Node.js version

21.1

### Operating system

Mac OS

### Apify platform

- [ ] Tick me if you encountered this issue on the Apify platform

### I have tested this on the `next` release

_No response_

### Other context

_No response_

[B4nan]

Creating the config instance itself is not enough, you need to use it in all the methods touching the storage. Alternatively, you can modify the global config instance:

Configuration.set('purgeOnStart', true); // FYI this is the default
Configuration.set('persistStateIntervalMillis', 10_000);
Configuration.set('storageClientOptions', { localDataDirectory: path.join(__dirname, ".tmp", "crawlee-data") });

Also this needs to happen before you touch any storage API.

[jo-sip]

Thanks, I just set it in the JSON as it was also recommended in the docs (and that worked), but your example might be better with the autocomplete/type safety.