Nestor Vera

I believe the last stable release was using `"@sanity/visual-editing": "^2.8.0"`: https://github.com/nuxt-modules/sanity/commit/c675cc5eadaf5296cf737ec42a57e4a4651d1d11#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519R56 The issue is probably related to the changes made for react compiler: https://github.com/sanity-io/visual-editing/blob/main/packages/visual-editing/CHANGELOG.md#280-2024-11-19 ~~Setting an override in `pnpm-workspace.yaml` seems...

@dependabot rebase

This change was implemented in https://github.com/zernonia/vue3-notion/commit/43eb4a577d3e70351d4c067820930c0ff6bdeead and released as part of https://github.com/zernonia/vue3-notion/releases/tag/v0.1.46

The requested functionality seems to be available in `imgproxy` via the [`brightness`](https://docs.imgproxy.net/usage/processing#brightness) and [`colorize`](https://docs.imgproxy.net/usage/processing#colorize) options. `colorize` is basically the equivalent of my proposed solution with `opacity` and `background`, only using...

> My assumption is that Storybook's vite always builds in "production" mode which triggers the "Missing NUXT_UI_PRO_LICENSE license key" condition, even if it runs as `storybook dev --port 6006`. Your...

Can't you do something like adding `* { transition-durantion: 0s; }` before changing the color scheme and remove it once that change is done?

You need to use v4 as noted on `README.md`: https://github.com/nuxt-modules/storybook/tree/4.x

@javag97 have you tried adding `@storybook/core` to your deps? Make sure to pin it to the following version: ```json "@nuxtjs/storybook": "4.3.2", "@storybook/addon-a11y": "6.5.16", // probably not required "@storybook/core": "6.5.16", ```

@danielroe we can close this now.

> > When generating a sandbox, it does not contain our default stories (Button, Header, Page), which some of our e2e-production tests require. Therefore, I was forced to disable our...