Strange behavior in imported tagged template

dhowe · February 8, 2021, 8:46am

I am experiencing some strange behavior when importing a tagged template from another notebook (the same tagged template works fine when created within the notebook). This notebook: Untitled / Daniel Howe / Observable demonstrates the problem with a minimal example.

Any insight would be appreciated

hellonearthis · February 8, 2021, 9:36am

When the like rsl = RiTa.template(md); is commented out, the imported rs works. It’s like the two versions don’t work together.

dhowe · February 8, 2021, 10:03am

I don’t see that… When I comment the rsl call, I get the same behavior (see below). And I actually noticed the problem when using `rs ` alone, so I don’t think this is the issue (though I could be wrong).

Cobus · February 8, 2021, 3:09pm

Interesting.For me, the headings don’t work in either example. And even in the Rita Utilities notebook, the headings don’t work (see below).

I am using Chrome

mbostock · February 8, 2021, 7:26pm

I tried to visit @dhowe/rita in Safari and it’s unable to load Rita due to a parsing error:

SyntaxError: Invalid regular expression: invalid group specifier name

I see the same thing as @Cobus in Chrome: it doesn’t render the headings on either of the two notebooks, and all the code behaves the same way.

dhowe · February 8, 2021, 9:43pm

Thanks much for everyone’s feedback. I think I’ve located in the issue in the library. The reason it was manifesting strangely was that different minor versions of the library were being loaded in the two examples.

Follow-ups:

is there a way to specify ‘the newest version’ for a require ?
is there a way to test (preferably in node) via the same `md` function as in the stdlib ? I’m currently using a tagged template I created from the `marked` lib on npm, but the behavior does not appear to be exactly the same

Cobus · February 9, 2021, 6:15am

You can just say:
RiTa = require("rita")
which would get you the newest version.

dhowe · February 9, 2021, 9:07am

That gets you the newest version at that moment. What I’m asking is if there is a way to keep in sync with the newest version…

Cobus · February 9, 2021, 2:27pm

I am not quite sure I understand the question then. It would load the newest version whenever you refresh your browser window (which would re-execute the ‘require’ call in the cell).

dhowe · February 9, 2021, 5:20pm

That doesn’t always seem to be the case. See below (directly after refresh):

Though this may relate to jsdelivr caching, which apparently can take up to 24 hrs

Cobus · February 9, 2021, 7:08pm

Ah, perhaps. This is what I get:

dhowe · February 9, 2021, 8:27pm

Was that a new notebook, or a an existing one that you refreshed? Because the jsdelivr cache has now refreshed with the new version and I still see previous versions in my notebooks after a page refresh:

Cobus · February 10, 2021, 5:45am

OK, so I think this is due to cacheing in the browser. Require actually loads from unpkg, and if you read the cacheing behavior here: https://unpkg.com it seems like the best advice is actually to specify the version in the require, otherwise it may just use the browser cached version.

mootari · February 11, 2021, 1:52pm

It does? Afaik d3-require defaults to cdn.jsdelivr.net. Only Observable’s import() override defaults to unpkg.com (when used without a hostname).

Cobus · February 11, 2021, 3:38pm

Indeed, you are right! Sorry for the misinformation. Ignore what I said about require using unpkg!