Is there an efficient way to discover which notebooks contain errors after republishing a dependency of those notebooks?
None immediately come to mind, unfortunately, but you can pin the version number of an import so that it always sees the same version of the notebook.
For example, to import the current version of the Vega-Lite API notebook, you can say:
import {vl} from "@vega/vega-lite-api@319"
To determine the latest version number, you can open the notebook’s history for a notebook you own, or you can download the code for a notebook and look at the included README.
In the not-so-distant future, our plan is to make version pinning happen automatically, so that notebook imports (and library requires!) are stable by default, even for transitive dependencies. It’s not a trivial task, however. Apologies for it not yet being available.
1 Like
How about a way to discover the notebooks directly and indirectly dependent upon a given notebook?