Tmk

it doesn't seem to be a problem, it depends on the order of rendering and storage accessing. `storageDemo` is a _reactive_ value, if you want to get the latest value,...

There is a real-world library([axios](https://github.com/axios/axios)) that supports both options simultaneously: ```ts import axios from 'axios'; axios .get('https://httpbin.org/delay/2', { // catch AxiosError: timeout of 1000ms exceeded timeout: 1000, // catch CanceledError:...

it's now unsupported :( https://github.com/antfu/vitesse-webext/issues/169#issuecomment-2029616706

updating the auto import config `'webextension-polyfill': [ ['*', 'browser'], ],` to `'webextension-polyfill': [ ['default', 'browser'], ],` works in dev, but breaks in production. it seems like a bug in the...

what's the error message?

Firefox doesn't support HMR in the dev mode of MV3. You need to run `EXTENSION=firefox pnpm build` to create a Firefox extension for production. https://bugzilla.mozilla.org/show_bug.cgi?id=1864284

hi @juliusmarminge, there are some vercel ci actions need authorization to deploy to pass the checks.

it shows a full path because the `framework` option is from `getAbsolutePath`. it's okay if we use `framework: 'storybook-react-rsbuild'` instead of `framework: getAbsolutePath('storybook-react-rsbuild')`  https://github.com/storybookjs/storybook/blob/a5c7f7fd16643c3aa85fceb9149e3d2e83b9ef7d/code/lib/core-server/src/build-dev.ts#L81

I mean it works as expected in user's projects. it shows the full path in this repo only. the users use `'storybook-react-rsbuild'` directly, which doesn't have this issue.

i see, this may occur in a monorepo which shares Storybook dependencies. agree with u that it's better to do something like `frameworkName.split(/[\\/]/).at(-1)` in storybook