`Execution context was destroyed` error occurs when running storycap.

[l4dybird]

Description

When running storycap with vue-component-meta enabled, the following error occurs:
error Execution context was destroyed, most likely because of a navigation.

Environment

• OS: Windows 11
• Node.js: 20.18.3
• Package Manager: pnpm 10.5.2
• Chrome: 133
• Storybook: 8.6.0
• Storycap: 5.0.1

Sample Repository

A sample repository reproducing this issue is available here:
nuxt3-sb8-quasar (clash/storycap branch)

Additional Context

• The error occurs when running storycap, even with default settings.
• This might be related to Puppeteer or Chrome compatibility.
• If you have any workarounds or insights, please let me know.

[l4dybird]

I have created a minimal sample.
https://github.com/l4dybird/vue-storybook-using-vue-component-meta

It seems that the issue can be avoided by modifying main.ts as follows:

"framework": {
  "name": "@storybook/vue3-vite",
  "options": {
    "docgen": "vue-docgen-api"
  }
}

[stackdiver]

Same issue here. We run latest storycap with react/next-js in a docker container timbru31/node-chrome.

error Execution context was destroyed, most likely because of a navigation.
Error: Execution context was destroyed, most likely because of a navigation.
at rewriteError (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/ExecutionContext.js:265:23)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async ExecutionContext._evaluateInternal (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/ExecutionContext.js:219:61)
at async DOMWorld.addStyleTag (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/DOMWorld.js:243:21)
at async CapturingBrowser.addStyles (/app/node_modules/storycap/lib/node/capturing-browser.js:56:13)
at async CapturingBrowser.reload (/app/node_modules/storycap/lib/node/capturing-browser.js:72:9)
at async Promise.all (index 0)
at async CapturingBrowser.setViewport (/app/node_modules/storycap/lib/node/capturing-browser.js:184:17)
at async CapturingBrowser.screenshot (/app/node_modules/storycap/lib/node/capturing-browser.js:329:31)

I tried some of the CLI options and found that enabling CSS animations would improve the runner reliability.
So by adding --disableCssAnimation true to the run command it passes.

Maybe the call in the above stack on CapturingBrowser.addStyles causes the issue, idk