builder-vite: Unable to load from fresh installation

Here is the package.json The error I started the project using this and choosing the react option.

npm init @vitejs/app vite-react-app --template react && cd vite-react-app
npm install # or yarn
npx sb@next init --builder storybook-builder-vite && npm run storybook

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 24 (8 by maintainers)

Commits related to this issue

Revert "Fix package duplication issues by aliasing all storybook packages (#160)" (#166) This reverts commit 5100593ce2067e46e2a0ff7608911bb39a70236c. As discussed in https://github.com/eirslett/s... — committed to storybookjs/builder-vite by IanVS 3 years ago

Most upvoted comments

@olemarius

The pertinent section of my package.json is:

{
  // ...
  "devDependencies": {
    "@storybook/addon-a11y": "6.4.0-rc.6",
    "@storybook/addon-docs": "6.4.0-rc.6",
    "@storybook/addon-essentials": "6.4.0-rc.6",
    "@storybook/addon-links": "6.4.0-rc.6",
    "@storybook/react": "6.4.0-rc.6",
    "@vitejs/plugin-react": "^1.1.0",
    "storybook-builder-vite": "^0.1.9",
    "typescript": "^4.4.4",
    "vite": "^2.6.14"
  },
  "resolutions": {
    "@storybook/csf-tools": "6.4.0-rc.6",
    "@storybook/source-loader": "6.4.0-rc.6",
    "@storybook/core-events": "6.4.0-rc.6"
  }
}

scott-lc on Nov 24, 2021

I’ve tried both

delete package-lock and node_modules
npm install
npx npm-force-resolutions
npm install
run storybook

and

delete package-lock and node_modules
npm install
npx npm-force-resolutions
run storybook

The IGNORED_EXCEPTION doesnt go away.

running npm-why ( https://github.com/amio/npm-why ) shows that all is the same version.

@shilman Also tried rc-7 now, can confirm it doesnt work either.

olemarius on Nov 24, 2021

I think the issue others are facing is due to not including the second npm install. If anyone is looking to use npm-force-resolutions I’d advise reading the usage guide: https://www.npmjs.com/package/npm-force-resolutions

joshwooding on Nov 23, 2021

@olemarius

As a workaround, add the following to your package.json file:

{
  "resolutions": {
    "@storybook/core-event": "6.4.0-rc.5",
    "@storybook/csf-tools": "6.4.0-rc.5",
    "@storybook/source-loader": "6.4.0-rc.5"
  }
}

If you are using yarn just re-install: yarn install; it automatically handles the “resolutions” field. If you are using npm, run npx npm-force-resolutions (and again after any change to your dependencies.) and then run npm install

npx npm-force-resolutions
npm install

See https://github.com/eirslett/storybook-builder-vite/issues/161#issuecomment-976987545 below.

scott-lc on Nov 23, 2021

We’ll be releasing 6.4 final very soon (later this week? early next?) which should hopefully help with this issue!

shilman on Nov 22, 2021

Nope then I’m back with this issue https://github.com/eirslett/storybook-builder-vite/issues/157

olemarius on Nov 20, 2021