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
I am currently using the midscene.js library, specifically the cache functionality as described in the documentation.
Problem:
I noticed that the cache is not working when the environment is not set to test. This behavior limits the ability to take advantage of the cache outside testing scenarios.
Question:
Is it possible to enable or apply the cache functionality outside of test environments? If not, could this feature be implemented in future versions?
Example:
Below is an example script where I would like to leverage the cache functionality:
export const scrapeWeb = async () => {
const browser = await chromium.launch();
const context = await browser.newContext();
const page = await context.newPage();
const webPage = new PlaywrightWebPage(page);
const agent = new PlaywrightAgent(webPage);
// Rest of the scraping logic...
};
Any guidance or clarification would be highly appreciated. Thank you for your support
The text was updated successfully, but these errors were encountered:
josegarridodigio
changed the title
Cache not working outside test environments - Feature Request or Clarification
[Feature Request or Clarification] - Cache not working outside test environments
Jan 10, 2025
Context:
I am currently using the midscene.js library, specifically the cache functionality as described in the documentation.
Problem:
I noticed that the cache is not working when the environment is not set to test. This behavior limits the ability to take advantage of the cache outside testing scenarios.
Question:
Is it possible to enable or apply the cache functionality outside of test environments? If not, could this feature be implemented in future versions?
Example:
Below is an example script where I would like to leverage the cache functionality:
Any guidance or clarification would be highly appreciated. Thank you for your support
The text was updated successfully, but these errors were encountered: