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

wso2_apim_publisher

v3.0.1

Published

WSO2 API Manager Publisher Web App Note: `eslint-plugin-react` have a fixed version due to implementing prop-types does mark nested destructed props from `eslint-plugin-react` next version onwards --max_old_space_size: This is max size of the old space(

Downloads

3

Readme

Publisher Portal Application Structure

  1. Override folder - If you want to override a certain React Component / file from source/src/ folder, this is the correct place to do it. You do not have to copy the entire directory, only copy the desired file/files.

  2. Services folder - Includes the files related to the functionalities of login, logout and refresh.

  3. Site folder - Includes the configuration and public folders of the project.

  4. jaggery.conf file - The file that is responsible to fetch the paths and handle server-side routing.

Note : Only the Services and Site folders along with the jaggery.conf file is required at the runtime.

  1. Source and other files - Includes the react files (source code) of the Publisher Portal React Application.