jupyterlab-jsoncrack
Advanced JSON, YAML, and CSV viewer for JupyterLab
Requirements
- JupyterLab >= 4.0.0
Install
To install the extension, execute:
pip install jupyterlab_jsoncrack
Uninstall
To remove the extension, execute:
pip uninstall jupyterlab_jsoncrack
Demo
A JupyterLite demo for this extension lives in demo. It
bundles the local package into a static site and configures JSON Crack as the
default opener for .json, .yaml, .yml, and .csv files so the viewer can
be explored directly in the browser.
Contributing
Development install
Note: You will need NodeJS to build the extension package.
This project uses pnpm as the package manager.
# Clone the repo to your local environment
# Change directory to the jupyterlab_jsoncrack directory
# Set up a virtual environment and install package in development mode
python -m venv .venv
source .venv/bin/activate
pip install --editable "."
# Link your development version of the extension with JupyterLab
jupyter labextension develop . --overwrite
# Rebuild extension Typescript source after making changes
# IMPORTANT: Unlike the steps above which are performed only once, do this step
# every time you make a change.
pnpm run build
You can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.
# Watch the source directory in one terminal, automatically rebuilding when needed
pnpm run watch
# Run JupyterLab in another terminal
jupyter lab
With the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).
By default, the pnpm run build command generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:
jupyter lab build --minimize=False
Development uninstall
pip uninstall jupyterlab_jsoncrack
In development mode, you will also need to remove the symlink created by jupyter labextension develop
command. To find its location, you can run jupyter labextension list to figure out where the labextensions
folder is located. Then you can remove the symlink named jupyterlab-jsoncrack within that folder.
AI Coding Assistant Support
This project includes an AGENTS.md file with coding standards and best practices for JupyterLab extension development. The file follows the AGENTS.md standard for cross-tool compatibility.
Compatible AI Tools
AGENTS.md works with AI coding assistants that support the standard, including Cursor, GitHub Copilot, Windsurf, Aider, and others. For a current list of compatible tools, see the AGENTS.md standard.
This project also includes symlinks for tool-specific compatibility:
CLAUDE.md→AGENTS.md(for Claude Code)
Other conventions you might encounter:
.cursorrules- Cursor's YAML/JSON format (Cursor also supports AGENTS.md natively)CONVENTIONS.md/CONTRIBUTING.md- For CodeConventions.ai and GitHub bots- Project-specific rules in JetBrains AI Assistant settings
All tool-specific files should be symlinks to AGENTS.md as the single source of truth.
What's Included
The AGENTS.md file provides guidance on:
- Code quality rules and file-scoped validation commands
- Naming conventions for packages, plugins, and files
- Coding standards (TypeScript)
- Development workflow and debugging
- Common pitfalls and how to avoid them
Customization
You can edit AGENTS.md to add project-specific conventions or adjust guidelines to match your team's practices. The file uses plain Markdown with Do/Don't patterns and references to actual project files.
Note: AGENTS.md is living documentation. Update it when you change conventions, add dependencies, or discover new patterns. Include AGENTS.md updates in commits that modify workflows or coding standards.
Packaging the extension
See RELEASE
Metadata
Release files for jupyterlab-jsoncrack 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| jupyterlab_jsoncrack-0.1.1.tar.gz | 2.9 MB | Without provenance | Details for jupyterlab_jsoncrack-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jupyterlab_jsoncrack-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for jupyterlab_jsoncrack-0.1.1-py3-none-any.whl |
Total release size: 4.2 MB
Release files / jupyterlab_jsoncrack-0.1.1.tar.gz
| Download URL | jupyterlab_jsoncrack-0.1.1.tar.gz |
|---|---|
| Size | 2.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f717ceb089ebc7a00bdce6d0d84b01bcd1f9e6e6af02675d0578dd3634a361e1
|
|
BLAKE2b-256 checksum How to use checksums |
fcf6c6bd2b20bb49e87e9a1b76e55d73b4c3539560fc342fa727fcef2db8a749
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Release files / jupyterlab_jsoncrack-0.1.1-py3-none-any.whl
| Download URL | jupyterlab_jsoncrack-0.1.1-py3-none-any.whl |
|---|---|
| Size | 1.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fc79e8fcb2823bb7f266229a9c517688b29f72a77b774e77b8db1d5665e88485
|
|
BLAKE2b-256 checksum How to use checksums |
d034eba43d7e6a9f08ec424c60db0e8db6593106f3d66e1f9a6b0613fefe7ed4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for jupyterlab-jsoncrack 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.