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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@piserve-tech/form-builder-webcomponent

v1.0.10

Published

Distributable web component build for form builder (bundle.js, bundle.css, fonts, icons)

Readme

Using the Form Builder Web Component from npm

  1. Install the npm package:

    npm install @piserve-tech/form-builder-webcomponent
  2. Add the following to your src/index.html inside the <head> tag:

    <link rel="stylesheet" href="node_modules/@piserve-tech/form-builder-webcomponent/dist/bundle.css">
    <script src="node_modules/@piserve-tech/form-builder-webcomponent/dist/bundle.js"></script>
  3. Copy the assets to your project (run after install):

    node ./node_modules/@piserve-tech/form-builder-webcomponent/copy-assets.js

    This will copy all required assets to src/assets/form-builder-webcomponent.

  4. Use the web component in your Angular templates:

    <form-builder-element></form-builder-element>
  5. Make sure your AppModule includes CUSTOM_ELEMENTS_SCHEMA:

    import { NgModule, CUSTOM_ELEMENTS_SCHEMA } from '@angular/core';
    // ...existing code...
    @NgModule({
      // ...existing code...
      schemas: [CUSTOM_ELEMENTS_SCHEMA]
    })
    export class AppModule {}

No Angular imports are needed from the npm package. The web component is loaded globally via the script tag.

AngularFormBuilderComponent

This project was generated with Angular CLI version 16.1.8.

Development server

Run ng serve for a dev server. Navigate to http://localhost:4200/. The application will automatically reload if you change any of the source files.

Code scaffolding

Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.

Build

Run ng build to build the project. The build artifacts will be stored in the dist/ directory.

Running unit tests

Run ng test to execute the unit tests via Karma.

Running end-to-end tests

Run ng e2e to execute the end-to-end tests via a platform of your choice. To use this command, you need to first add a package that implements end-to-end testing capabilities.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI Overview and Command Reference page.

Form Builder Library

Created a library named formBuilder inside the form builder component project.

Asset Management

To avoid overwriting existing assets, all library assets (icons, fonts, etc.) are copied to a dedicated folder: src/assets/form-builder-webcomponent.

After installing the library, run the following command to copy assets:

node ./node_modules/@piserve-tech/form-builder-webcomponent/copy-assets.js

This will copy all assets from the library's npm package to your app's src/assets/form-builder-webcomponent folder.

You can add this command to your project's postinstall script for automation:

	"scripts": {
		"postinstall": "node ./node_modules/@piserve-tech/form-builder-webcomponent/copy-assets.js"
	}

Library Usage

Inside the library we have created modules and components for the layout design and also a service folder for the API services.

To export a service from the library for accessing it in installed projects, specify the path of the service in the library's package.json file.

If any changes are made to the library, build it using:

ng build formBuilder

After building, update the version of the library in the package.json file of the library.

To publish the library, open a terminal from the formBuilder folder inside the dist folder and use:

npm publish

to publish it to the npm registry.