Core: Theme updates don't invalidate manager caching
See original GitHub issue6.1 includes manager caching, where the manager UI is only built on changes to the manager config. However, changing the theme doesn’t invalidate the cache.
Reproduction
Set up a fresh CRA install and add a theme to .storybook/manager.js
:
import { addons } from "@storybook/addons";
import { themes } from "@storybook/theming";
addons.setConfig({
theme: themes.dark,
});
Run yarn storybook
and cache the manager.
Then update the theme:
addons.setConfig({
theme: themes.light,
});
Observe that it is still using the original cached manager, rather than re-caching to reflect the change.
Workaround
As a workaround you can run yarn storybook --no-manager-cache
to manually invalidate.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:30
- Comments:20 (6 by maintainers)
Top Results From Across the Web
Core: Theme updates don't invalidate manager caching #13200
As a workaround you can run yarn storybook --no-manager-cache to manually invalidate. Update comments. I am using version 6.1.11.
Read more >How to invalidate the client cache with release of a new version?
Hi Javascript-Experts, After releasing a new Version, I am facing the issue that (JS) files in the Browser Cache do not update immediately....
Read more >Flag links don't invalidate cache [#3142283] | Drupal.org
As far as I understand it, this is because Internal Dynamic Page Cache is caching the rendered content. Clicking on the Flag link...
Read more >WordPress Changes Not Showing? 3 Methods to Fix It Right ...
Some caching plugins clear the cache for updates, including posting a blog entry, adding comments, and customizing the theme. However, your ...
Read more >WordPress Changes Not Showing? Here's How to Fix ... - Kinsta
Most web hosts and caching plugins get around this by automatically “clearing” the cache whenever you publish or update a piece of content....
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 Free
Top 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
Delete the
.cache
folder fromnode_modules
, run the storybook again, it should solve the problem.I am using version 6.1.11
After adding
--no-manager-cache
with start command, it continues to sayinfo => Using cached manager
and the theme doesn’t update.Does anyone have a viable solution, I have tried everything, clearing storage, hard-refreshing, but the problem seems to be in storybook cache managemnt.