I am currently starting a new project and decided to work with the latest Angular (13 at this moment) and my next steps will require me to make a JSON editor ... or use one
I saw your repo fork and I also see that for Angular 13 support but it says "Work in Progress" and there is no npm command for Angular 13.
$ ng serve
⠙ Generating browser application bundles (phase: setup)...(node:39691) UnhandledPromiseRejectionWarning: Error: The target entry-point "@maaxgr/ang-jsoneditor" has missing dependencies:
- jsoneditor
at TargetedEntryPointFinder.findEntryPoints (file://{path-to-angular-project}/test-json-editor/node_modules/@angular/compiler-cli/bundles/ngcc/index.js:4616:13)
at file://{path-to-angular-project}/test-json-editor/node_modules/@angular/compiler-cli/bundles/ngcc/index.js:5008:33
at SingleProcessExecutorSync.doExecute (file://{path-to-angular-project}/test-json-editor/node_modules/@angular/compiler-cli/bundles/ngcc/index.js:14633:23)
at file://{path-to-angular-project}/test-json-editor/node_modules/@angular/compiler-cli/bundles/ngcc/index.js:14654:35
at SyncLocker.lock (file://{path-to-angular-project}/test-json-editor/node_modules/@angular/compiler-cli/bundles/ngcc/index.js:14884:14)
at SingleProcessExecutorSync.execute (file://{path-to-angular-project}/test-json-editor/node_modules/@angular/compiler-cli/bundles/ngcc/index.js:14654:19)
at mainNgcc (file://{path-to-angular-project}/test-json-editor/node_modules/@angular/compiler-cli/bundles/ngcc/index.js:15985:19)
at Module.process2 (file://{path-to-angular-project}/test-json-editor/node_modules/@angular/compiler-cli/bundles/ngcc/index.js:16050:10)
at NgccProcessor.processModule ({path-to-angular-project}/test-json-editor/node_modules/@ngtools/webpack/src/ngcc_processor.js:182:27)
at {path-to-angular-project}/test-json-editor/node_modules/@ngtools/webpack/src/ivy/host.js:146:18
(Use `node --trace-warnings ...` to show where the warning was created)
(node:39691) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:39691) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
⠇ Generating browser application bundles (phase: setup)...