Feedback for /builders/vite docs page

[storybook-bot]

👍	👎
9	9

[storybook-bot]

/docs/react/builders/vite

👍	v7.0	react	ts

async viteFinal(config)

css: {
// added some global scss mixins
}

[storybook-bot]

/docs/7.0/vue/builders/vite

👍	v7.0	vue	ts

[storybook-bot]

/docs/7.0/vue/builders/vite

👍	v7.0	vue	ts

[storybook-bot]

/docs/7.0/react/builders/vite

👍	v7.0	react	ts

Info about vite config

[storybook-bot]

/docs/7.4/react/builders/vite

👍	v7.4	react	ts

[storybook-bot]

/docs/7.4/react/builders/vite

👍	v7.4	react	ts

[storybook-bot]

/docs/7.4/react/builders/vite

👎	v7.4	react	ts

Doesn't work

[storybook-bot]

/docs/7.5/react/builders/vite

👍	v7.5	react	ts

[storybook-bot]

/docs/7.5/react/builders/vite

👎	v7.5	react	ts

[storybook-bot]

/docs/7.5/react/builders/vite

👎	v7.5	react	ts

many issues with doc gen. somehow babel is trying to take it's place back

[storybook-bot]

/docs/7.5/builders/vite

👎	v7.5	vue	ts-4-9

automaticArgTypeInference link is broken

[usrrname]

tis I, curmudgeon

[jonniebigodes]

Thanks for taking the time to reach out to us and letting us know of this situation. We appreciate it 🙏 . I have a pull request that is currently addressing the issue, which will fix not only the currently available links for the latest release (7.6) but also for the pre-release documentation. I'm truly sorry for this inconvenience.

[storybook-bot]

/docs/7.6/builders/vite

👎	v7.6	react	ts

It didn't explain what I need to configure in the vite.config

[jonniebigodes]

Thanks for reaching out to us with your feedback. We appreciate it 🙏 ! However, can you or someone else facing a similar situation provide additional context on this so we can adjust the documentation if need be? However, if you're referring to the configuration Vite config file, Storybook will automatically import and apply what's defined in said file, which you can also, split based on the environment you're working with (e.g., development, production). Also, documenting every single option available for every use case would quickly turn into a maintenance burden trying to match every use case possible.

[storybook-bot]

/docs/7.6/builders/vite

👍	v7.6	react	ts

[storybook-bot]

/docs/8.0/builders/vite

👍	v8.0	vue	ts

[storybook-bot]

/docs/8.1/builders/vite

👎	v8.1	html	js

Seems to be outdated? Fresh install, ran doctor, and it complained about Storybook using deprecated things. I literally just installed T.T There's also no good examples of just HTML+Vite, or using just plain HTML at all; it's all super focused on frameworks.

[storybook-bot]

/docs/8.1/builders/vite

👎	v8.1	html	js

No help for how to use with vite plugins

[storybook-bot]

/docs/8.1/builders/vite

👎	v8.1	react	ts-4-9

This page is out of date, according to the Storybook documentation. https://storybook.js.org/docs/api/main-config-core#builder

You no longer use core, and installing SB via npx reflects that - the framework is set, not the core.builder.

Also "the builder is already installed and configured for you" is misleading and confusing. What does that mean exactly? I don't see it installed when I do an npx installation, so is there some magic the builder package provides? It's just a bit confusing if you're trying to migrate or try different builders out.

[storybook-bot]

/docs/builders/vite

👎	v8.4	react	ts