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

@lcsga/ng-utils

v1.0.0

Published

Provides Angular utils

Downloads

1

Readme

@lcsga/ng-utils

types

This package provides a set utility types for angular.

  • ExtractRouteInputs: Extracts the route's path parameters, the resolved values and the data values to create an object type to implement in @Components

    Example:

    // app.routes.ts
    
    const userRoute = {
      path: 'user/:id' as const,
      data: { someData: true },
      resolve: { user: () => of({ name: 'Lucas', age: 26 }).pipe(delay(500)) },
      loadComponent: () => import('./user.component'),
    } satisfies Route;
    
    export type UserRouteInputs = ExtractRouteInputs<typeof userRoute>;
    /* Output:
      {
        id: string:
        someData: boolean;
        user: {
          name: string;
          age: number;
        }
      }
    */
    
    export const routes: Routes = [userRoute];

    In the example above, we can see two import things to extract the route inputs:

    • the use of { ... } satisfies Route instead of a basic userRoute: Route => this is really important to let typescript infer the type of userRoute but still keeping autocompletion and type validation during the development phase
    • the use of as const for the path: it helps typescript infer 'user/:id' instead of string => it's necessary to extract id as the path param input

    This ExtractRouteInputs is composed of the flattened:

    NB: Since query parameters are not declared in a Route we cannot extract them.