fix: cache-bust the nodeps nbextension bundles - #1170
Merged
Conversation
The requirejs urlArgs hash lookup only matched */extension ids, so the nodeps bundles (which contain the actual widget frontends, mapped via requirejs config) were served without any version parameter - browsers keep serving a stale cached copy after the extension updates, which breaks pages in ways that show no console error. The extension directory hash already covers the nodeps files; normalize the id so they resolve to it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
maartenbreddels
temporarily deployed
to
fix/nbextension-nodeps-cache-busting - solara-stable PR #1170
July 4, 2026 14:04 — with
Render
Destroyed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The requirejs
urlArgscache-busting only matched*/extensionmodule ids, so the nodeps bundles — which contain the actual widget frontends and are loaded via the requirejsmapconfig (jupyter-vue→nbextensions/jupyter-vue/nodeps) — were requested without any version parameter. Browsers then keep serving a stale cached copy after the extension is updated, which breaks pages in ways that show no console error (e.g. a widget manager waiting forever on a model the old bundle doesn't have — the page just sits at "Loading app").The extension-directory hash already covers the nodeps files (it hashes every file in the extension directories), so the fix is to normalize the module id: strip the
nbextensions/prefix variants and map<ext>/nodepsto<ext>/extensionbefore the hash lookup.Verified locally:
nodeps.jsis now requested asnodeps.js?<hash>and stale-cache pages recover on a plain reload.Found while working on ES module support for ipyvue (#1169), where every frontend rebuild was silently masked by this.
🤖 Generated with Claude Code