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

orgbrain-pjl-frontend

v0.1.11

Published

Pauls attempt at making a basic resuable Orgbrain layout and login. Forked from orgbrain-frontend. Adds ogin authorisation and app switching

Downloads

7

Readme

Pjl-Frontend

Pauls attempt at making a basic resuable Orgbrain layout and login. Forked from orgbrain-frontend. Adds ogin authorisation and app switching

To test

$ npm start

To deploy library

Edit the version in package.json

$ npm run lib $ npm run publish

To use

$ npm install orgbrain-pjl-frontend

The OrgbrainFrontEnd

This is a template layout which can be used to standardise the orgbrain apps.

How to use the Orgbrain frontend module

The OrgBrainPjlFrontEndModule is defined by the lib.module.ts

There are other useful modules e.g. OrgBrainLogoModule

The entry point for your app inside the orgbrain-app-selection modify your app.module.ts like this

  bootstrap: [RootComponent]

Providing components for the OrgBrainFrontend

orgbrain-root

This label defines the main component used by the orgbrain-app-selection

@Component({
  selector: 'orgbrain-root',
  template: ` <router-outlet #fullwindowoutlet name=\"fullwindow\"> 
   </router-outlet> <orgbrain-defaultlayout *ngIf=\"!useFullWindowOutlet\"> </orgbrain-defaultlayout> `,
  styles: ['']
})

class MyMainComponent  . . . 

Router outlets

We can also inject other components into the orgbrain-app-selection by defining outlets in our route.

e.g.

[TODO understand this better what is available how does it work?]

 RouterModule.forRoot([
      {
        path: '',
        component: ContentDemoComponent    // this appears in the main router outlet (see above)
      },
      {
        path: '',
        pathMatch: 'full',
        outlet: 'leftsidemenu',
        component: MenuDemoComponent
      },
      {
        path: '',
        outlet: 'toolbar',
        component: ToolbarDemoComponent
      },
      {
        path: 'tabs',
        children: [    // ??? need to look into what this is doing
          {
            path: '',
            outlet: 'extratoolbars',
            component: ExtraToolbarComponent
          },
          {
            path: 'dashboard',
            component: DashboardComponent,
          },
          {
            path: 'reports',

            children: [
              {
                path: '',
                component: ReportsComponent
              },
              {
                path: '',
                outlet: 'leftsidemenu',
                component: ReportsMenuComponent
              }
            ]
          }
        ]
      },
      {
        path: 'fullwindowtest',
        outlet: 'fullwindow',
        component: ContentDemoComponent
      }
    ]),

Authentication / Logon

Logon can be triggered by using the canActivate feature of the router. (Probably other ways but this allows you to select which routes require authentication).

e.g.

 RouterModule.forRoot([
      {
        path: '',
        canActivate: [AuthGuardService],
        component: ContentDemoComponent
      },

Trying to navigate to a path calls the canActivate method of the AuthGuardService.