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

@realcommerce/rc-utils

v1.0.16

Published

A collection of UI components / directives / pipes

Downloads

25

Readme

##rcUtils package

A collection of UI components / directives / pipes

Install

npm i @realcommerce/rc-utils --save

Api

import { RcUiModule } from '@realcommerce/rc-utils'; 

@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    BrowserModule,
    RcUtilsModule
  ],
  providers: [],
  bootstrap: [AppComponent]
})
export class AppModule { }

Services

  • rc-auth.service

makes the calls to the server and saves the token to the storage you should inject the environemt with the baseUrl field ie: ###Example


@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    BrowserModule,
    RcUtilsModule
  ],
  providers: [{ provide: 'ENVIRONMENT', useValue: environment },
  ....
],
  bootstrap: [AppComponent]
})

environment.ts :

export const environment = {
  baseUrl: 'http://localhost:xxx/',
};

then you can inject and use it, note that it is used by rc-login (check rc-login documentation) so you can just use the rc login for the default implementation.

the endpoints in the server should have the following signature (if needed):

api.post(this.authUrl + '/Login', { username, password, recaptchaToken }) api.post(this.authUrl + '/OTPSend', { username: username, phoneNumber, recaptchaToken }) api.post(this.authUrl + GenerateToken`, userClaims); api.get(this.authUrl + '/RefreshToken', headers: new HttpHeaders().set('refreshToken', refreshToken) })

Interceptors

  • jwt.interceptor

adds bearer token to each request, caches the request in case of 401 to try to refresh the token, then if the refresh succeded - processes the cached request again. if you want to use it you should provide the interceptor ie:

@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    BrowserModule,
    RcUtilsModule
  ],
  providers: [{ provide: HTTP_INTERCEPTORS, useClass: JwtInterceptor, multi: true },
  ....
],
  bootstrap: [AppComponent]
})

###Example

Authors

Zion Ben Yacov, Yacov Barboi