Recently, @kappelmann and I were discussing a notebook where it would be convenient to import a different notebook depending on user input, e.g. something like this (or maybe with more specialized syntax): import {cell} with {...} from `${toggle ? 'notebook1' : 'notebook2' }` instead of: im…

I don’t have a great answer for you right now, @bgchen — but I just wanted to let you know that this sort of thing is an important topic that we’ve been thinking through quite seriously. To briefly describe the problem space: Observable notebooks are versioned, but can load code and data in many w…

If I might add my two cents: I think the current import with syntax should be deprecated and replaced with an import helper in the stdlib or runtime that works similarly to d3-require (and would likely just end up being a custom resolver?). Let’s be honest, the current syntax is confusing as hell w…

+1 for this, what should one do for conditional imports right now?

This might help: [image] Dataflow An Observable notebook by Mike Bostock.

I imagine this may also apply to “lazy” imports. Right now notebook imports get transcoded to static imports, which means that every referenced notebook gets fetched, even if none of its cells are imported.

Feature request: conditional imports

Feedback

mootari September 13, 2019, 6:02pm 3

Topic		Replies	Views
Are all dependencies imported when I import another notebook? Feedback	4	1043	November 28, 2018
In defense of static imports Feedback	10	2271	December 22, 2020
import as viewof etc. Community Help	10	351	October 7, 2022
can i swap out `import ... from` value, or does it have to be manually entered? Community Help	5	622	August 29, 2020
Can a class defined in a notebook be imported? Community Help	4	595	July 21, 2020

Feature request: conditional imports

Related topics