ngx-view-builder
v0.6.0
Published
Moved. Split in 0.5.0 and renamed to @ngxviewbuilder/runtime and @ngxviewbuilder/designer in 0.6.0.
Maintainers
Readme
ngx-view-builder
This package moved. It was split in two in 0.5.0, and in 0.6.0 both halves moved under the @ngxviewbuilder npm scope. It no longer ships any code.
| Install | When |
| --- | --- |
| @ngxviewbuilder/runtime | Your app renders saved views. Free, no license key. |
| @ngxviewbuilder/designer | Your app also lets people edit them. |
npm rm ngx-view-builder
npm i @ngxviewbuilder/runtimeAdd the designer only where views are actually edited:
npm i @ngxviewbuilder/designerWhy
The old package contained both the runtime and the drag-and-drop editor, so every production build shipped the editor even when users never opened it. Splitting them means an app that only renders views no longer carries the editor.
The 0.6.0 move to the @ngxviewbuilder scope reserves the namespace: nobody else can publish anything under @ngxviewbuilder/, which closes off look-alike package names.
What changes in your code
Inputs, outputs, component selectors and your saved JSON are unchanged. Views saved by older versions migrate automatically on load. Only the import source and the stylesheet path move:
-import { NgxViewBuilderRuntime, IStructure } from 'ngx-view-builder';
+import { NgxViewBuilderRuntime, IStructure } from '@ngxviewbuilder/runtime';-import { NgxViewBuilderBuilder, BuilderModel } from 'ngx-view-builder';
+import { NgxViewBuilderDesigner, BuilderModel } from '@ngxviewbuilder/designer';-@import 'ngx-view-builder/styles/index.css';
+@import '@ngxviewbuilder/runtime/styles/index.css';The editor component was renamed to <ngx-view-builder-designer> / NgxViewBuilderDesigner in 0.5.1, with the old <ngx-view-builder-builder> selector and class name kept as working aliases. The selectors themselves did not change in 0.6.0 — only the package names did.
The designer re-exports the runtime's public API, so a file that uses both can keep a single import from @ngxviewbuilder/designer. Files that only render should import from @ngxviewbuilder/runtime directly, which is what keeps the editor out of your bundle.
Documentation
https://ngxviewbuilder.io
- Developer guide: https://ngxviewbuilder.io/developers/
- Live demo: https://ngxviewbuilder.io/demo
