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

lvd-core-test

v0.0.5

Published

LVD Core uses PrimeNG and PrimeFlex to provide a set of core application components that can be used in all Leveldata applications.

Downloads

27

Readme

LvdCore

This library was generated with Angular CLI version 17.2.0.

Code scaffolding

Run ng g c component-name --flat --path projects/lvd-core/component-name/src --project lvd-core to generate a new component in the lvd-core library. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module --project lvd-core.

Note: Don't forget to add --project lvd-core or else it will be added to the default project in your angular.json file.

If you need to create a new library you can run ng generate library library-name from the workspace directory. If your library requires multiple entry points please refer to the following link https://sandroroth.com/blog/angular-library/?ref=dailydev#main-entry-point for guidance in building the library or just follow the structure from lvd-core

Build Library

Run npx -p @angular/cli@17 ng build library-name to build the project. The build artifacts will be stored in the dist/ directory.

Showcasing And Debugging Your Feature

Run ng g m features/lazy-<component-name> --route <component-name> --module app --project showcase to create a lazy loaded module so that you can see your view and test your feature on the showcase app.

Configure the newly created module and component to use your library component and run ng g m features/lazy-activity-feed --route activity-feed --module app --project showcase

Run npx -p @angular/cli@17 ng build library-name --watch to build your library, then run npm start to fire up the showcase app. Any changes you make to the library should be picked up by the showcase app.

Build Showcase

Run ng build —project showcase —named-chunks —output-hashing none to build the showcase app, you should see the size of your component under the lazy loaded feature.

Publishing

After building your library with npx -p @angular/cli@17 ng build library-name, go to the dist folder cd dist/library-name and run npm publish.

If you are publishing to Azure Artifacts make sure you include the .npmrc for the feed in the dist/library-name folder.

Running unit tests

Run ng test library-name to execute the unit tests via Karma.

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.