Does Storybook cache its change by port number somewhere hidden?

[adamchenwei]

Describe the bug
I can't reproduce it, but I can tell what happened:
so I had two identical application repo (repo#1 and repo#2), repo#1 was running on 9001 already with a vue component call Hello established, while the repo #2 haven't yet setup storybook yet. So once I configed storybook in repo#2, then stopped the repo #1's storybook and started storybook for repo #2 afterward, for some reason the old change in repo #1 is showing up in the repo#2's storybook instance on 9001 (I am like what in the world?>???????)
So I stopped repo #2 storybook and change port to 9002 in config. it reports now, an error of depedency with babel was not found... while it did not have issue before and storybook was running an old version of my component, and after I installed the missing babel, now I gets problem parsing sass inside vue component

So I wonder is storybook caching itself somewhere that we should always clean it if we are having two repo with somehow similiar storybook setup?

To Reproduce
Not able to reproduce atm

Expected behavior
to expect to build correctly

System:

• OS: MacOS
• Device: MacBook Pro
• Browser: Chrome
• Framework: Vue
• Addons: none
• Version: 4.0.4

[adamchenwei]

I am not sure what that is, but adding custom webpack config for sass fixed it, its here:https://storybook.js.org/configurations/custom-webpack-config/