Note that you can provide a name for unnamed functions, e.g.: {name: 'peek',}. Alternatively you can change peek() to a named function.

In practice, this doesn't work very well. Dependencies start failing, and this is something to do with the d3-require cache note being shared across the additional runtimes.

Does this help? https://github.com/observablehq/stdlib/issues/274#issuecomment-1148134998 and

... Nevermind, seems this is already happening via the Object.assign on the library instance.

Could it be that the lazy loading in some of your static imports messes with the instance?

Specifically the one in the testing suite?

I don't use the function "peek" anymore, the testing lazy loading usually works because it naturally is done last so hopefully doesn't use new modules too much. I mark this as bad just because someone recently liked this notebook so I want to steer people away from it. I kinda want to delete it but thats perhaps too far.

> the testing lazy loading usually works because it naturally is done last I'd be careful with that assumption. Multiple requires can load scripts simultaneously and override each other's window.define (which gets set anew on *every* require() call).