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

@555platform/portal-components

v1.0.4

Published

Shared portal components

Downloads

4

Readme

portal-components

A library of components that are shared across portals

Project Status

Build

Contributing

Requires node v10+

Installation

This project contains multiple child projects. You can install dependencies for all of the nested projects by running npm run install_all. This will install all necesary dependencies, and link the projects in the lib folder into the demo project.

git clone [email protected]:555platform/portal-components.git
nvm use 8.11
npm run install_all

Creat a demo/server/.env with the following settings (environment dependent)

CLIENT_ID=<INSERT>
CLIENT_SECRET=<INSERT>
DOMAIN=pop.service.srv
REDIRECT_URI=http://localhost:4044/auth/iris/callback
AUTH_SERVER=http://localhost:4655
EKSURL=http://localhost:3007
PORT=4044
LOGIN_SUCCESS=http://localhost:4050/dashboard
LOGIN_FAILURE=http://localhost:4050/
JWT_PUBLIC_KEY=<INSERT>
LOG_FOLDER=logs
LOG_ROTATION_POLICY="YYYY-MM-DD"
SERVER_NAME=localhost:4044
DATABASE_URIS="localhost:27017"
DATABASE_NAME=identities
DB_USER=""
DB_PASSWORD=""
DATABASE_REPLSET=""

Creat a demo/client/.env.development.local with the following settings (environment dependent)

REACT_APP_CLIENT_ID=<INSERT>
REACT_APP_DOMAIN=pop.service.srv
REACT_APP_REDIRECT_URI=http://localhost:4044/auth/iris/callback
REACT_APP_AUTH_SERVER=http://localhost:4655

Workflow (Standalone)

  1. Update files in lib/server and/or lib/client.
  2. Build your changes
# from the root of the `portal-components` project
npm run build
  1. Run the demo application
# from the root of the `portal-components` project
npm start

Note: Live reloading is set up for the demo app code only. Changes to files under demo/ should be picked up immediately, however changes to any of the code under lib/ will require a rebuild. Be sure to run npm run build from the root of the project whenever you make changes to lib code!

Workflow (Portal integration)

When you are ready to integrate your component(s) with one of the portals:

  1. Link portal-components
# from the root of the `portal-components` project
npm link
  1. Build any changes
    1. Manual build
    # from the root of the `portal-components` project
    npm run build
    1. Automatic rebuild
    # from the root of the `portal-components` project
    npm run watch
  2. From a local clone of either pop or developer-portal, link portal-components as a dependency
# from the root of either pop or developer-portal
npm link portal-components
cd client
npm link portal-components
  1. You can now import your common code e.g import { client as clientCommon } from 'portal-components'.