npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

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.

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/runtime

Add the designer only where views are actually edited:

npm i @ngxviewbuilder/designer

Why

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