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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@smallstack/ng-wc-serve

v1.3.0

Published

Serves all files (main, vendor, polyfill...) from the angular dev server endpoint as a single concatinated file via ngrok for angular web component testing purposes

Downloads

21

Readme

Angular Web Component Serve CLI

At smallstack we develop web components and plug them into our backoffice applications. Instead of replicating our applications & microservices for local development, we want to reference our local web components online in our applications, hence this CLI.

How does it work?

An express server serves all angular files (runtime.js, polyfills.js, styles.js, scripts.js, vendor.js, main.js) as one concatinated file at http://localhost:4250/webcomponent. This endpoint now gets proxied via ngrok to a random ngrok address which can be used in our applications. Websockets are proxied as well, so live-mode is possible.

Installation

npm i -g @smallstack/ng-wc-serve

Have a look at the inline help: ng-wc-serve --help. Since version 1.1.x ngrok is disabled by default and has to be enabled via --ngrok

Endpoints

  • /webcomponent: serves files as concatinated file
  • /health: returns 200 OK (e.g. if used with https://github.com/bahmutov/start-server-and-test)

Guide

  1. To make the concatination process work, you need to run your angular dev server in production mode. At least you have to set optimization=true and sourceMap=false during the ngcc process, otherwise you'll run into js file parsing issues in your browser (Cannot parse <). We also need to disable the host check when ngrok is used, otherwise it won't work. Create a new script called start:wc in your angular project and add the following content: "ng serve --optimization=true --sourceMap=false [--disableHostCheck=true --no-live-reload]". Adjust the command as much as you want to, e.g. set a project or additional build parameters.
  2. Start the CLI (in any folder) via ng-wc-serve, you'll see something like this: Command Line Screenshot
  3. Follow the instructions and start the Angular Dev Server as described
  4. Now you can copy the ngrok address and get started

Debugging

Debugging your your web component can be hard since the code is minified. If you turn of angular's optimizations, this whole setup won't work anymore. Instead, you can turn off several build switches and still create a production bundle:

  • NG_BUILD_MANGLE=false
  • NG_BUILD_MINIFY=false
  • NG_BUILD_BEAUTIFY=false