Provide `.ipynb` file support out of the box

[joyceerhl]

Work items

• Built-in extension that ships with VS Code and that can be disabled but not uninstalled
  - Support both web and desktop
  - Starter code https://github.com/joyceerhl/vscode-jupyter-notebook-serializer
• Built-in support for creating a new Jupyter notebook via the New File... flow
• ms-toolsai.jupyter cleanup
  • Deregister our serializer Don't register our jupyter-notebook serializer vscode-jupyter#6778
  • Delay native notebooks survey notification when users dismiss (eventually remove survey) Clicking 'x' should be equivalent to clicking No on survey prompts and survey should not show for interactive window vscode-jupyter#6767
  • Do not update workbench.editorAssociations setting based on experiment (VS Code will continue to cache) Remove code to configure workbench.editorAssociations based on experiment status vscode-jupyter#6768
• New Jupyter notebook getting started experience in VS Code
  • Recommend Jupyter extension if missing renderers for output mimetypes
  • Recommend kernel extensions in order to run code
  • Fix existing notification to install Jupyter extension for ipynb files (shows only for json, not for notebook editor UI which is the default experience today)
  • Syntax highlighting for ipynb json
• Restore custom editor backup with ipynb serializer @rebornix
  • Remove custom editor contribution in Jupyter extension (after testing)

Deferred

• Jupyter and builtin ipynb extension to depend on a common npm package providing utilities for converting between VS Code notebook types and nbformat
  • Reimplement create new and export without serializer Remove notebook serializer from Jupyter extension vscode-jupyter#6756

[rebornix]

We would also want to support syntax highlighting ipynb when it's opened in a text editor. We would need a grammar which can be identical to JSON (but we can't add ipynb as a file ext option for JSON ext otherwise it will break save).

[joyceerhl]

Discussion items from meeting with @DonJayamanne and @roblourens:

• Supporting newer versions of nbformat
  • Not currently necessary but in future this extension will need to be updated fairly regularly as nbformat ships updates
• Notebook and cell metadata
  • The current serializer adds metadata under a custom property
  • Some of this is done to support .NET Interactive scenarios, e.g. see Do the best to save .NET output into ipynb format vscode-jupyter#6196
  • No immediate plans to change this but if we do we should inform .NET Interactive team and others
• Compression of cell outputs on save
  • IIRC Don mentioned doing some compression of outputs on save rather than at the time that the outputs are updated, the built-in serializer will not do this

[rebornix]

re

Compression of cell outputs on save
IIRC Don mentioned doing some compression of outputs on save rather than at the time that the outputs are updated, the built-in serializer will not do this

maybe it's related to terminal outputs which we currently compress in notebook controllers, which leads to performance issue. We may want to just do this on save.

[roblourens]

@rebornix what do you mean it will "break save" if we call ipynb files JSON?

[joyceerhl]

@roblourens if we call ipynb files JSON, when doing Save As on an untitled Jupyter notebook, the file picker attempts to save it as JSON by default and fails with an error.

[rebornix]

@joyceerhl already gave it a good summary. The issues tracking them are:

• No syntax highlighting for ipynb No file association for .ipynb #122589 and my original fix was adding ipynb to the JSON file extension list, which caused below issue
• Native Notebooks - Can't save a newly created notebook #124918

[davidanthoff]

Quick question: does this essentially mean that if a user has VS Code and the Julia extension installed, they would no longer even need the Jupyter extension to work with Jupyter notebook files?