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

odigo

v0.0.1

Published

This project was generated with [Angular CLI](https://github.com/angular/angular-cli) version 11.0.0-rc.2.

Downloads

41

Readme

Odigo

This project was generated with Angular CLI version 11.0.0-rc.2.

Pasos para construir un angular web element

ng new odigo ng add @angular/elements ng g component analytics-counter --inline-style --inline-template -v Native ng build --prod --output-hashing none

Se añade en el root concatenate.js que hace el empaquetamiento del web element, una libreria js mas una css, también podría contener assets

npm install fs-extra concat --save-dev

Añadimos el siguiente scrip a package.json: { "scripts": { ... "build:elements": "ng build --prod --output-hashing none && node concatenate.js" }, } }

Y por último para realizar el bundle correctamente se ejecuta el siguiente comando

npm run build:elements

Para lanzar las pruebas con una página html que incorpore el web element y lo utilice, se deben seguir los siguientes pasos

npm install http-server -g Ejecutar http-server (esto lanza un servidor web en el puerto 8080 y ejecuta el index.html en el root.Este index.html es el que tiene la incoporación del web element)

Development server

Run ng serve for a dev server. Navigate to http://localhost:4200/. The app 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. Use the --prod flag for a production build.

Build and pack as javascript/css library

npm run build:elements

Create component web element

ng g component analytics-counter --inline-style --inline-template -v Native

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 Protractor.

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.