question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Core: Theme updates don't invalidate manager caching

See original GitHub issue

6.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:closed
  • Created 3 years ago
  • Reactions:30
  • Comments:20 (6 by maintainers)

github_iconTop GitHub Comments

18reactions
utkarshabakcommented, Jan 13, 2021

I am still having the same issue, adding --no-manager-cache not updating my theme updates, I want to update the Logo, is there any other way to replace it?

Delete the .cache folder from node_modules, run the storybook again, it should solve the problem.

5reactions
utkarshabakcommented, Jan 7, 2021

I am using version 6.1.11

After adding --no-manager-cache with start command, it continues to say info => 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.

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found