5 ms·
Legitimately very cool. As someone else mentioned I’d also really like the ability to embed these on another page, and possibly have these run locally offline.
by dyarosla 9y ago
Legitimately very cool. As someone else mentioned I’d also really like the ability to embed these on another page, and possibly have these run locally offline.
I do have a question: for notebooks linking to outside notebooks: is there anything that prevents breakages? Ie external notebook variable name changes or is completely removed, would parts of my notebook relying on that one then also fail? Is there some kind of public versioning of notebooks so that I can refer to a value at notebook ref,v1?
- jashkenas 9y agoThat's a fantastic question. It's not ready yet, but we're hoping to roll out import pinning for notebooks soon. Each notebook is versioned — every time you make a change and re-run the cell, a version is saved to the server. And every time you publish, that's a publication of a specific version of the notebook. Our plan is to pin the version of any code you import from outside the notebook, including require(npm-module), import {value} from "other-notebook", and even the version of the Observable standard library that was current when you wrote the notebook. Hopefully, that should provide a good foundation for robust notebooks that don't break as libraries change over time. Of course, you'll be able to re-pin a new version if you want to upgrade something.
- dyarosla 9y agoAwesome. Thanks for replying. I'll definitely be watching your team at work :)