Theme is cached between unrelated instances
See original GitHub issueDescribe the bug
When running multiple Storybook projects, the logo from one project is shown in another. Investigation shows that the logo URL is stored in @storybook/ui/store
in LocalStorage, which explains why this happens.
To Reproduce Steps to reproduce the behavior:
- Setup a Storybook with a custom
brandImage
and run it locally. - Setup another Storybook with default config.
- Kill the first Storybook, run the second on the same port.
- The custom logo from the first appears on this completely unrelated Storybook.
Expected behavior The second project should show the default Storybook logo.
System: Mac OS, Chrome
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:20 (12 by maintainers)
Top Results From Across the Web
Moodle in English: Problem with theme cache on boost child theme
Moodle can cache themes, language strings, filters and other bits of information that have been calculated and stored by the web browser.
Read more >About overriding themable output - Drupal
Note that Drupal maintains cached theming, data through the theme registry. It must be cleared when setting up overrides.
Read more >Caching in AEM as a Cloud Service - Experience League
When the publish instance receives a new version of a page or asset from the author, it uses the flush agent to invalidate...
Read more >Page Cache and Replication
The sites, as determined programmatically, of storefronts that offer products from the product catalog. The page caches of unrelated storefront sites aren't ...
Read more >Cache | Screen-by-Screen | LSCache for WordPress
This option will cache any PHP resources loaded by themes. Generally speaking, these are css or js resources loaded in PHP. In most...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I figured out to fix this removing
node_modules/.cache/storybook
I didn’t know about the--no-manager-cache
flag, thank you @shilman@ndelangen is working on a solution in 5.3! 🎉