Runing into NWjs fails by npm but works by CDN

[DanielBanobreDopico]

General information

• json-editor version: 2.3.0

Expected behavior

Calling new JSONEditor(documentSection,{schema: schema}) must build a form.

Actual behavior

Raise Error: element should be an instance of Element
=====> BUT if I use CDN instead npm, It works. <=====

Steps to reproduce the behavior

npm install @json-editor/json-editor --save

const JSONEditor = require('@json-editor/json-editor').JSONEditor;
const documentSection = document.getElementById('documentSection');
const schena = '{"type":"object","required":["x","y"],"properties":{"x":{"type":"number"},"y":{"type":"number"}}}';
new JSONEditor(documentSection,{schema: schema})

Notes:

documentSection instanceof Element returns true
=====>>> It's running in NWjs <<<======

[Klapauzius]

Encountering the same issue, even though JSONEditor is loaded via import '@json-editor/json-editor';

Stepping back versions in npm, the last working one was 2.1.0.

[marc7000]

In my Vue.js / NW.js (Webpack) application i use the following import and it works:
import { JSONEditor } from '@json-editor/json-editor/dist/jsoneditor.js'

Init:

this.elem = this.$refs['json-editor-element']
this.jsonEditor = new JSONEditor(this.elem, {
    schema: this.schema,
    theme: 'bootstrap4',
    iconlib: 'fontawesome5'
})
this.jsonEditor.on('change', this.onChange)

[marc7000]

I use JSONEditor 2.2.1 and it also works with 2.3.0

[Klapauzius]

@marc7000 - you put your finger on the issue:
With versions <= 2.1.0, the statement import '@json-editor/json-editor'; was sufficient.
With versions > 2.1.0, the statement import { JSONEditor } from '@json-editor/json-editor'; is required.

Now - knowing this - I updated my code base and am fine.

Would it be possible to maybe extend the github documentation or the npm documentation with the appropriate import statement? When it stopped working on this update I went hunting, but couldn't find the import statement in the documentation...
Probably it's obvious to any experiences JavaScript programmer (which sadly I'm not ;-) ).

[marc7000]

Probably something has changed in refactoring of the build task.
Yeah, we should include it in the documentation as soon as possible.

[nickelnext]

Do you know how to make it work with Nuxtjs?

[marc7000]

@nickelnext
I have no experience with NuxtJs but I think it should also work as explained above.

[germanbisurgi]

Closing this but feel free to reopen