31:T45d,md`## Embeds You can now [download your notebook](/@jashkenas/downloading-and-embedding-notebooks) as a standalone ES module or npm-compatible tarball, letting you host or embed your live, interactive notebook *anywhere*! You can even embed Observable notebooks with bidirectional control in [React apps](/@jashkenas/how-to-embed-a-notebook-in-a-react-app), [Idyll docs](https://mathisonian.github.io/observable-idyll/), [CodePen](https://codepen.io/jashkenas/pen/gzZXPG), [Jekyll](https://visionscarto.net/observable-jekyll/) and more. To enable embeds and other creative uses of notebooks, we’ve open-sourced the Observable [runtime](https://github.com/observablehq/notebook-runtime) and [inspector](https://github.com/observablehq/notebook-inspector). The runtime *runs* code—it orchestrates the [topological evaluation of cells](/@mbostock/how-observable-runs)—while the inspector lets you *inspect* the resulting values—it displays human-readable objects, numbers, whatever. (Our [standard library](https://github.com/observablehq/notebook-stdlib) was already open-source.) Send us your pull requests!`32:T8d6,md`## Interface improvements If you no longer want your unpublished changes, you can now revert your notebook to its published state: choose Revert from the header’s notebook menu . You can likewise revert unshared changes to shared notebooks. To make it easier to dispose of unwanted notebooks, we’ve added a Trash option. (As before, you can also trash your notebooks from any listing.) These changes are only a small step towards better nondestructive editing of notebooks; stay tuned! [Giving a presentation?](/@mbostock/slide) Try the new Fullscreen mode, also in the notebook menu. This uses the [fullscreen API](https://developer.mozilla.org/docs/Web/API/Fullscreen_API) to make your notebook content fill the screen. (You can also use your browser’s built-in fullscreen mode, which limits the content to the center column to allow access to the margin’s editing controls.) For notebooks that use experimental features, such as [asynchronous iteration](/@mbostock/introduction-to-asynchronous-iteration) and [arbitrary-precision integers](/@tmcw/solving-project-euler-20-with-bigints), we now display a helpful warning to readers whose browser does not support the needed feature. Lastly, we’ve upgraded to the [0.10.0-beta release of ${tex`\KaTeX`}](https://github.com/Khan/KaTeX/releases/tag/v0.10.0-beta) and tweaked the font size for better readability when mixing math and prose.`33:[] 2f:{"title":"Changelog 2018-06-12","cells":[{"id":0,"value":"md`# Changelog 2018-06-12\n\nWelcome back to the [Changelog](/collection/changelog), where we cover recent improvements and new features for Observable notebooks! Love it? 😍 Hate it? 😡 Let us know [on the forum](https://talk.observablehq.com/) or [by email](mailto:support@observablehq.com).`","pinned":false,"hidden":false,"mode":"ojs"},{"id":201,"value":"md`## Highlights\n\nBut first, here’s a quick highlight of some of the amazing notebooks you all have been publishing recently.\n\nNoah Veltman beautifully explains [how to place labels along shape centerlines](/@veltman/centerline-labeling). Florian Ledermann teaches you [how to draw your first map](/@floledermann/drawing-maps-from-geodata-in-d3). Erin Caughey [proves #MidwestIsBest](/@erincaughey/merged-midwestisbest-map). Herb Susmann explores the [*Boids* flocking model](/@herbps10/boids). Benjamin F. Maier proposes [an improvement to fisheye distortion](/@benmaier/a-visually-more-appealing-fisheye-function). Jim R. Wilson does a deep dive on the [seasonality in Bitcoin prices](/@jimbojw/the-seasons-of-bitcoin). And Elias Levy uses a Sankey diagram to visualize [voting in San Francisco’s mayoral election](/@eliaslevy/2018-san-francisco-major-ranked-choice-voting).\n`","pinned":false,"hidden":false,"mode":"ojs"},{"id":9,"value":"$31","pinned":false,"hidden":false,"mode":"ojs"},{"id":33,"value":"$32","pinned":false,"hidden":false,"mode":"ojs"},{"id":14,"value":"md`## Code improvements\n\nThe standard library now includes a [visibility promise](https://github.com/observablehq/notebook-stdlib/blob/master/README.md#visibility) that resolves when the current cell becomes visible in the browser’s viewport. By [awaiting visibility](/@mbostock/intersection-observer), you can have an animation start on scroll, or avoid expensive computation when a cell is offscreen. For example:`","pinned":false,"hidden":false,"mode":"ojs"},{"id":266,"value":"{\n await visibility();\n return html`

Hello, world!`;\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":295,"value":"md`(This example uses CSS animation, but you can use JavaScript, too.)`","pinned":false,"hidden":false,"mode":"ojs"},{"id":270,"value":"html``","pinned":true,"hidden":false,"mode":"ojs"},{"id":263,"value":"md`We’ve added dependency version resolution to [require](https://github.com/observablehq/notebook-stdlib/blob/master/README.md#require): now when you require a library with a dependency, we use the library’s package.json to load a *compatible* version of the dependency; previously, we always loaded the *latest* version.\n\nResolving the URL of a required library is now asynchronous, so we’ve deprecated the resolve method in the standard library and added [require.resolve](https://github.com/observablehq/notebook-stdlib/blob/master/README.md#require_resolve), which returns a promise to the resolved URL. For example, the URL of the latest version of D3 is:`","pinned":false,"hidden":false,"mode":"ojs"},{"id":17,"value":"require.resolve(\"d3\")","pinned":true,"hidden":false,"mode":"ojs"},{"id":29,"value":"md`There’s also a new [require.alias](https://github.com/observablehq/notebook-stdlib/blob/master/README.md#require_alias) method which is useful for requiring modules with [stubborn dependencies](/@tmcw/requiring-modules-troubleshooting), such as React.\n\nAs a reminder, we also support [ES dynamic import](https://github.com/tc39/proposal-dynamic-import) and we recommend it, if your browser supports it and your libraries are available as [ES modules](http://exploringjs.com/es6/ch_modules.html). We look forward to the future where code “just works” in any ES environment, and we’re working to realize that future by encouraging library authors to publish browser-compatible ES module bundles!\n\nThanks for reading, thanks for using Observable, and thanks for [your feedback](https://talk.observablehq.com/)! 🙏`","pinned":false,"hidden":false,"mode":"ojs"}],"files":"$W33","stdlib":"1","titling":"auto"}