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

corede-common-cocrm

v1.8.79

Published

The common utility functions, interfaces, types etc of cocrm project.

Downloads

13,831

Readme

corede-common-cocrm

Responsibilities

  1. This is main package that frontend will be using.

     - So that that should not be anything that are backend specific
     - There can be static functions that are used in backend but may be used in frontend.
     - But the general idea is to add everything related to frontend only or frontend+backend
  2. Data that needs to be here.

     1. All of the common interfaces
     2. All of the resolver input and result interfaces
     3. All of the common enum definitions
     4. All of the query strings. this query strings will be used by:
        
             - frontend to send request to backend server
             - backend for tests
    
     5. All of the utility functions that are not dependant on backend specific data or structure
     6. All of the common types.