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

system-navigator

v0.1.0

Published

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 10.1.6. Github repo, in case you want to meddle with it: https://github.com/viettranisnottaken/system-navigator

Downloads

17

Readme

SystemNavigator

This library was generated with Angular CLI version 10.1.6. Github repo, in case you want to meddle with it: https://github.com/viettranisnottaken/system-navigator

Code scaffolding

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

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

Build

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

Publishing

After building your library with ng build system-navigator, go to the dist folder cd dist/system-navigator and run npm publish.

Running unit tests

Run ng test system-navigator to execute the unit tests via Karma.

Usage

You can either call API for the urls, or just pass them in via @Input()

Getting urls by calling API

  1. Add SystemNavigatorModule to the module that you wish to use it in and use forChild({ api: 'someUrl'}) to pass in the url of the API that will provide information about the applications icons on the menu:

    ...
        import { SystemNavigatorModule } from 'system-navigator';
    
        @NgModule({
            declarations: [
                ...
            ],
            exports: [
                ...
                SystemNavigatorModule,
            ],
            providers: [
                HtmlClassService,
            ],
            imports: [
                ...
                SystemNavigatorModule.forChild({ api: 'https://sample-api.com/urls', headers: {'SomeHeader': '123'} }),
            ]
        })
        export class ThemeModule {
        }
  2. Add <lib-system-navigator></lib-system-navigator> to where you want to use it.

  3. Wrap a div around <lib-system-navigator></lib-system-navigator> to style it however you want. Like this:

    <div class="menu-container">
        <lib-system-navigator></lib-system-navigator>
    </div>

Passing data in @Input()

  1. Add SystemNavigatorModule to the module that you wish to use. No need to run forChild()

    ...
        import { SystemNavigatorModule } from 'system-navigator';
    
        @NgModule({
            declarations: [
                ...
            ],
            exports: [
                ...
                SystemNavigatorModule,
            ],
            providers: [
                HtmlClassService,
            ],
            imports: [
                ...
                SystemNavigatorModule,
            ]
        })
        export class ThemeModule {
        }
  2. Add <lib-system-navigator [inputAppUrls]="appUrls"></lib-system-navigator> to where you want to use it. appUrls has to be an Observable<AppUrl[]>

    appUrls = of([
        {
        name: "admin",
        url: "https://google.com",
        image: null
        },
        {
        name: "marketing platform",
        url: "https://www.youtube.com/watch?v=kXYiU_JCYtU",
        image: "https://photo-1-baomoi.zadn.vn/w1000_r1/2020_05_04_105_34923369/882279561615ff4ba604.jpg"
        },
        {
        name: "marketing platform",
        url: "https://www.youtube.com/watch?v=kXYiU_JCYtU",
        image: "https://photo-1-baomoi.zadn.vn/w1000_r1/2020_05_04_105_34923369/882279561615ff4ba604.jpg"
        },
    ]),

    or

        constructor(private http: HttpClient, private appService: AppService) {
            this.inputAppUrls = this.getUrls();
        }
    
        getUrls(): Observable<AppUrl[]> {
            return this.appService.getUrls(this.api, this.headers);
        }
  3. Wrap a div around <lib-system-navigator [inputAppUrls]="appUrls"></lib-system-navigator> to style it however you want. Like this:

    <div class="menu-container">
        <lib-system-navigator [inputAppUrls]="appUrls"></lib-system-navigator>
    </div>

APIs

The library expect a response like this from your api:

{
  "status": true,
  "message": "ok",
  "httpCode": 200,
  "data": [
    {
      "name": "admin",
      "url": "https://google.com",
      "urlLogo": null
    },
    {
      "name": "marketing platform",
      "url": "https://www.youtube.com/watch?v=kXYiU_JCYtU",
      "urlLogo": "https://photo-1-baomoi.zadn.vn/w1000_r1/2020_05_04_105_34923369/882279561615ff4ba604.jpg"
    },
    {
      "name": "marketing platform",
      "url": "https://www.youtube.com/watch?v=kXYiU_JCYtU",
      "urlLogo": "https://photo-1-baomoi.zadn.vn/w1000_r1/2020_05_04_105_34923369/882279561615ff4ba604.jpg"
    },
  ],
  "errorCode": "ok"
}

Here are some interfaces

export interface AppUrl {
    name: string;
    url: string;
    urlLogo?: any;
    id?: number;
    index?: number;
}

export interface ServerResponse {
    status?: boolean;
    message?: string;
    httpCode?: number;
    data: AppUrl[];
    errorCode?: string;
}

Plans for next version

- Themes can be imported