A web-based tool to view, edit, format, transform, and validate JSON
The library is written with Svelte, but can be used in any framework (React, Vue, Angular, plain JavaScript).
Install via npm:
npm install svelte-jsoneditor
- Svelte examples: /src/routes/examples
- Plain JavaScript examples: /examples/browser
- React example: https://codesandbox.io/s/svelte-jsoneditor-react-59wxz
Create a JSONEditor with two-way binding bind:json
:
<script>
import { JSONEditor } from 'svelte-jsoneditor'
let content = {
text: undefined, // used when in code mode
json: {
array: [1, 2, 3],
boolean: true,
color: '#82b92c',
null: null,
number: 123,
object: { a: 'b', c: 'd' },
string: 'Hello World'
}
}
</script>
<div>
<JSONEditor bind:content />
</div>
Or one-way binding:
<script>
import { JSONEditor } from 'svelte-jsoneditor'
let content = {
text: undefined, // used when in code mode
json: {
greeting: 'Hello World'
}
}
function handleChange(updatedContent, previousContent, patchResult) {
// content is an object { json: JSONData } | { text: string }
console.log('onChange: ', updatedContent, previousContent, patchResult)
content = updatedContent
}
</script>
<div>
<JSONEditor {content} onChange="{handleChange}" />
</div>
The library provides a standalone bundle of the editor which can be used in any browser environment and framework. In a framework like React, Vue, or Angular, you'll need to write some wrapper code around the class interface.
Browser example loading the ES module:
<!DOCTYPE html>
<html lang="en">
<head>
<title>JSONEditor</title>
</head>
<body>
<div id="jsoneditor"></div>
<script type="module">
import { JSONEditor } from 'svelte-jsoneditor/dist/jsoneditor.js'
let content = {
text: undefined,
json: {
greeting: 'Hello World'
}
}
const editor = new JSONEditor({
target: document.getElementById('jsoneditor'),
props: {
content,
onChange: (updatedContent, previousContent, patchResult) => {
// content is an object { json: JSONData } | { text: string }
console.log('onChange', updatedContent, previousContent, patchResult)
content = updatedContent
}
}
})
// use methods get, set, update, and onChange to get data in or out of the editor.
// Use updateProps to update properties.
</script>
</body>
</html>
Svelte component:
<script>
import { JSONEditor } from 'svelte-jsoneditor'
</script>
<div>
<JSONEditor {content} />
</div>
JavasScript class:
import { JSONEditor } from 'svelte-jsoneditor/dist/jsoneditor.js'
const editor = new JSONEditor({
target: document.getElementById('jsoneditor'),
props: {
content,
onChange: (updatedContent, previousContent, patchResult) => {
// content is an object { json: JSONData } | { text: string }
console.log('onChange', updatedContent, previousContent, patchResult)
}
}
})
-
content: Content
Pass the JSON contents to be rendered in the JSONEditor. Contents is an object containing a propertyjson
andtext
. Only one of the two must be defined. In case oftree
mode,json
is used. In case ofcode
mode,text
is used. -
mode: 'tree' | 'code'
. Open the editor in'tree'
mode (default) or'code'
mode. -
mainMenuBar: boolean
Show the main menu bar. Default value istrue
. -
navigationBar: boolean
Show the navigation bar with, where you can see the selected path and navigate through your document from there. Default value istrue
. -
statusBar: boolean
Show a status bar at the bottom of the'code'
editor, showing information about the cursor location and selected contents. Default value istrue
. -
readOnly: boolean
Open the editor in read-only mode: no changes can be made, non-relevant buttons are hidden from the menu, and the context menu is not enabled. Default value isfalse
. -
indentation: number
Number of spaces use for indentation when stringifying JSON. -
escapeControlCharacters: boolean
. False by default. Whentrue
, control characters like newline and tab are rendered as escaped characters\n
and\t
. Only applicable for'tree'
mode, in'code'
mode control characters are always escaped. -
escapeUnicodeCharacters: boolean
. False by default. Whentrue
, unicode characters like โ and ๐ are rendered escaped like\u260e
and\ud83d\ude00
. -
validator: function (json: JSONData): ValidationError[]
. Validate the JSON document. For example use the built-in JSON Schema validator powered by Ajv:import { createAjvValidator } from 'svelte-jsoneditor' const validator = createAjvValidator(schema, schemaDefinitions)
-
onError(err: Error)
. Callback fired when an error occurs. Default implementation is to log an error in the console and show a simple alert message to the user. -
onChange(content: Content, previousContent: Content, patchResult: JSONPatchResult | null)
. The callback which is invoked on every change made in the JSON document. The parameterpatchResult
is only available intree
mode, and not intext
mode, since a change in arbitrary text cannot be expressed as a JSON Patch document. -
onChangeMode(mode: 'tree' | 'code')
. Invoked when the mode is changed. -
onClassName(path: Path, value: any): string | undefined
. Add a custom class name to specific nodes, based on their path and/or value. -
onRenderValue(props: RenderValueProps) : RenderValueComponentDescription[]
EXPERIMENTAL! This API will most likely change in future versions.
Customize rendering of the values. By default,
renderValue
is used, which renders a value as an editable div and depending on the value can also render a boolean toggle, a color picker, and a timestamp tag. Multiple components can be rendered alongside each other, like the boolean toggle and color picker being rendered left from the editable div. Built in value renderer components:EditableValue
,ReadonlyValue
,BooleanToggle
,ColorPicker
,TimestampTag
,EnumValue
.For JSON Schema enums, there is a value renderer
renderJSONSchemaEnum
which renders enums using theEnumValue
component. This can be used like:import { renderJSONSchemaEnum, renderValue } from 'svelte-jsoneditor' function onRenderValue(props) { // use the enum renderer, and fallback on the default renderer return renderJSONSchemaEnum(props, schema, schemaDefinitions) || renderValue(props) }
-
onRenderMenu(mode: 'tree' | 'code', items: MenuItem[]) : MenuItem[] | undefined
. Callback which can be used to make changes to the menu items. New items can be added, or existing items can be removed or reorganized. When the function returnsundefined
, the originalitems
will be applied.A menu item
MenuItem
can be one of the following types:-
Button:
interface MenuButtonItem { onClick: () => void icon?: FontAwesomeIcon text?: string title?: string className?: string disabled?: boolean }
-
Separator (gray vertical line between a group of items):
interface MenuSeparatorItem { separator: true }
-
Space (fills up empty space):
interface MenuSpaceItem { space: true }
-
-
queryLanguages: QueryLanguage[]
.
Configure one or multiple query language that can be used in the Transform modal. The library comes with three languages:import { jmespathQueryLanguage, lodashQueryLanguage, javascriptQueryLanguage } from 'svelte-jsoneditor' const allQueryLanguages = [jmespathQueryLanguage, lodashQueryLanguage, javascriptQueryLanguage]
By default, only
javascriptQueryLanguage
is loaded. -
queryLanguageId
. Theid
of the currently selected query language. -
onChangeQueryLanguage: (queryLanguageId: string) => void
. Callback function invoked when the user changes the selected query language in the TransformModal via the configuration button top right. -
onFocus()
callback fired when the editor got focus. -
onBlur()
callback fired when the editor lost focus.
-
get(): Content
Get the current JSON document. -
set(content: Content)
Replace the current content. Will reset the state of the editor. See also methodupdate(content)
. -
update(content: Content)
Update the loaded content, keeping the state of the editor (like expanded objects). You can also calleditor.updateProps({ content })
. See also methodset(content)
. -
patch(operations: JSONPatchDocument) : JSONPatchResult
Apply a JSON patch document to update the contents of the JSON document. A JSON patch document is a list with JSON Patch operations. -
updateProps(props: Object)
update some or all of the properties. Updatedcontent
can be passed too; this is equivalent to callingupdate(content)
. Example:editor.updateProps({ readOnly: true })
-
expand([callback: (path: Path) => boolean])
Expand or collapse paths in the editor. Thecallback
determines which paths will be expanded. If nocallback
is provided, all paths will be expanded. It is only possible to expand a path when all of its parent paths are expanded too. Examples:editor.expand(path => true)
expand alleditor.expand(path => false)
collapse alleditor.expand(path => path.length < 2)
expand all paths up to 2 levels deep
-
transform({ id?: string, selectedPath?: [], onTransform?: ({ operations: JSONPatchDocument, json: JSONData, transformedJson: JSONData }) => void, onClose?: () => void })
programmatically trigger clicking of the transform button in the main menu, opening the transform model. If a callbackonTransform
is provided, it will replace the build-in logic to apply a transform, allowing you to process the transform operations in an alternative way. If provided,onClose
callback will trigger when the transform modal closes, both after the user clicked apply or cancel. If anid
is provided, the transform modal will load the previous status of thisid
instead of the status of the editors transform modal. -
scrollTo(path: Path)
Scroll the editor vertically such that the specified path comes into view. The path will be expanded when needed. -
findElement(path: Path)
Find the DOM element of a given path. Returnsnull
when not found. -
acceptAutoRepair(): Content
In tree mode, invalid JSON is automatically repaired when loaded. When the repair was successful, the repaired contents are rendered but not yet applied to the document itself until the user clicks "Ok" or starts editing the data. Instead of accepting the repair, the user can also click "Repair manually instead". Invoking.acceptAutoRepair()
will programmatically accept the repair. This will trigger an update, and the method itself also returns the updated contents. In case of code mode or when the editor is not in an "accept auto repair" status, nothing will happen, and the contents will be returned as is. -
refresh()
. Refresh rendering of the contents, for example after changing the font size. This is only available incode
mode. -
focus()
. Give the editor focus. -
destroy()
. Destroy the editor, remove it from the DOM.
type JSONData = { [key: string]: JSONData } | JSONData[] | string | number | boolean | null
type TextContent = { text: string } | { json: undefined; text: string }
type JSONContent = { json: JSONData } | { json: JSONData; text: undefined }
type Content = JSONContent | TextContent
type Path = Array<string | number | symbol>
type JSONPatchDocument = JSONPatchOperation[]
type JSONPatchOperation = {
op: 'add' | 'remove' | 'replace' | 'copy' | 'move' | 'test'
path: string
from?: string
value?: JSONData
}
type JSONPatchResult = {
json: JSONData
previousJson: JSONData
undo: JSONPatchDocument
redo: JSONPatchDocument
}
type ValidationError = {
path: Path
message: string
isChildError?: boolean
}
type QueryLanguage = {
id: string
name: string
description: string
createQuery: (json: JSONData, queryOptions: QueryLanguageOptions) => string
executeQuery: (json: JSONData, query: string) => JSONData
}
type QueryLanguageOptions = {
filter?: {
path?: string[]
relation?: '==' | '!=' | '<' | '<=' | '>' | '>='
value?: string
}
sort?: {
path?: string[]
direction?: 'asc' | 'desc'
}
projection?: {
paths?: string[][]
}
}
interface RenderValuePropsOptional {
path?: Path
value?: JSONData
readOnly?: boolean
enforceString?: boolean
selection?: Selection
searchResult?: SearchResultItem
isSelected?: boolean
isEditing?: boolean
normalization?: ValueNormalization
onPatch?: TreeModeContext['onPatch']
onPasteJson?: (pastedJson: { path: Path; contents: JSONData }) => void
onSelect?: (selection: Selection) => void
onFind?: (findAndReplace: boolean) => void
}
interface RenderValueProps extends RenderValuePropsOptional {
path: Path
value: JSONData
readOnly: boolean
enforceString: boolean | undefined
selection: Selection | undefined
searchResult: SearchResultItem | undefined
isSelected: boolean
isEditing: boolean
normalization: ValueNormalization
onPatch: (patch: JSONPatchDocument) => void
onPasteJson: (pastedJson: { path: Path; contents: JSONData }) => void
onSelect: (selection: Selection) => void
onFind: (findAndReplace: boolean) => void
}
type ValueNormalization = {
escapeValue: (any) => string
unescapeValue: (string) => string
}
type SearchResultItem = {
path: Path
field: Symbol
fieldIndex: number
start: number
end: number
}
interface RenderValueComponentDescription {
component: SvelteComponent
props: RenderValuePropsOptional
}
The editor can be styled using the available CSS variables. A full list with all variables can be found here:
For example, to change the default blue theme color to anthracite:
<script>
import { JSONEditor } from 'svelte-jsoneditor'
let content = {
text: undefined, // used when in code mode
json: {
string: 'Hello custom theme color :)'
}
}
</script>
<div class="my-json-editor">
<JSONEditor bind:content />
</div>
<style>
.my-json-editor {
/* define a custom theme color */
--jse-theme-color: #383e42;
--jse-theme-color-highlight: #687177;
}
</style>
The editor comes with a built-in dark theme. To use this theme:
- Load the css file of the dark theme:
themes/jse-theme-dark.css
- Add the class name
jse-theme-dark
of the dark theme to the HTML container element where the editor is loaded.
It is possible to load styling of multiple themes, and toggle them by changing the class name (like jse-theme-dark
) attached to the HTML container element.
Full Svelte example:
<script>
import { JSONEditor } from 'svelte-jsoneditor'
let content = {
text: undefined, // used when in code mode
json: {
string: 'Hello dark theme :)'
}
}
</script>
<!-- use a theme by adding its name to the container class -->
<div class="my-json-editor jse-theme-dark">
<JSONEditor bind:content />
</div>
<style>
/* load one or multiple themes */
@import 'svelte-jsoneditor/themes/jse-theme-dark.css';
</style>
This library josdejong/svelte-jsoneditor
is the successor of josdejong/jsoneditor
. The main differences are:
josdejong/jsoneditor |
josdejong/svelte-jsoneditor |
|
---|---|---|
Creation | Orginal (first published in 2011) | Successor (first published in 2021) |
Framework | Implemented in plain JavaScript, using low level DOM operations | Uses Svelte |
Tree mode | A tree view having context menu buttons on the left of every line. The keys and values are always in editable state. | A tree view utilizing right-click to open the context menu, and double-click to start editing a key or value (more similar to a Spreadsheet or text editor). It supports copy/paste from and to the system clipboard. |
Code mode | Powered by Ace editor | Powered by Code Mirror 6 |
Preview mode | Used to preview large documents | Not needed, both Tree mode and Code mode can handle large documents |
The main reasons to create a new library instead of extending the existing one are:
- The codebase had become hard to maintain, the architecture needed a big overhaul. The codebase uses plain JavaScript to create and update the DOM based on changes in the state of the application. This is complex. Letting a framework like Svelte do this for you makes the code base much simpler.
- Performance limitations in the old editor.
- Tree mode: the classic tree mode of
josdejong/jsoneditor
is simple and straightforward, but also limited. The new tree mode ofjosdejong/svelte-jsoneditor
allows for much more streamlined editing and interaction. It works quite similar to a Spreadsheet or text editor. Navigate and select using the Arrow and Shift+Arrow keys or by dragging with the mouse. Double-click (or press Enter) to start editing a key or value. Open the context menu by right-clicking on the item or selection you want to operate on. Use cut/copy/paste to move parts of the JSON around and interoperate with other applications. - Code mode: the Ace editor library is using an outdated module system (AMD) and the way it is bundled and published is hard to integrate in modern JavaScript projects. Code Mirror 6 is very straightforward to integrate, has much better performance, and is very extensible (paving the way for future features).
Clone the git repository
Install dependencies (once):
npm install
Start the demo project (at http://localhost:3000):
npm run dev
Build the library:
npm run package
Run unit tests:
npm test
Run linter:
npm run lint
Publish to npm (will increase version number and publish to npm):
npm run release
Released under the ISC license.