Mike Bostock

Can you please re-merge main and resolve the conflicts? I can’t review this because it now includes a copy of all the other changes.

I’m not sure this is right. The virtual DOM and the real DOM aren’t the same; this is confusing concepts. (Maybe it would make sense if JSX produced real DOM,...

I don’t see a reason to duplicate state in this example. Also, you wouldn’t want a `Counter` component that hard-codes a reference to `updateUpstreamValue`; a component implies reusability, but hard-coding...

Related https://vanillajsx.com/

Precedence: ``` # literal request /data/foo.csv # first look for exact matches for each interpreter /data/foo.csv.js /data/foo.csv.py /data/foo.csv.go # parameterized data loader /data/[user].csv.js --user=foo # look for parameterized parents (1)...

Starting to head down the rabbit hole… 🎩 🐇 🤔 So far, this PR implements dynamic routing for data loaders: you can say _e.g._ `FileAttachment("foo.json")` and it will be served...

The purpose of parameterized pages is essentially to enable parameterized data loaders (through relative paths as described in my previous comment). If we enumerate the parameter values in the config,...

As another example, say you have the parameterized page `/[user]/index.md` which references the file `./foo.txt`. If this is a static file, _i.e._ there exists the file `/[user]/foo.txt` in the source...

I’ve thought of another challenge of trying to share static resources across parameter values. If a parameterized page imports a JavaScript component, we want that JavaScript component to be considered...

I want to try leaning into parameterization. I think the answer here is that we don’t try to share static assets across parameters; if you have `/[user]/foo.png`, it’s duplicated to...