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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@phoenix-cg/service

v1.0.0

Published

Phoenix-cg network service class

Readme

Services

All services are classes that extend base class Service.

Url configuration

Urls and configuration params located in /front_sources/src/conf.env.js: frontendBaseURL - url for frontend services, browser will make requests to this host. backendTestServer - url for express. If browser make requests to local server, that server will proxy requests to this host. backendMockServer - postman mock server url. It works this way: 1. local server try to make request to backendTestServer and 2. If it fails then (if usePostmanMock flag is true) make request to backendMockServer usePostmanMock - flag to use or not postman mock server useLocalMocks - you can additionaly have local mocks, this flag controls to load or not requests with them.

Service interface

Service has inner properties that could be useful:

|Property name | Description |--------------|------------- |namespace | Common part of the url, it will be placed first when constructing the url (e.g. if namespace is 'catalog' and unique url part is 'fields', result url will '/catalog/fields/') |isDev | If you need to change url if mode is development, there is a flag for it. |http | Axios instance, in most cases you will not need it but if you do, there it is.

Service has two main methods you will work with: get and post.

get method takes 2 arguments: url part and config. In config you can pass the parameters in params field. post method takes 3 arguments: url part, FormData payload and config.

Url part should not have slashes.

For example:

  class CommonService extend Service {
    async getTabs (id) {
      return this.get('tabs', { params: { id } })
    }
    async sendFeedback (payload) {
      return this.post('feedback', payload)
    }
  }

You can combine services and models:

  class CommonService extend Service {
    async getTabs (id) {
      const data = this.get('tabs', { params: { id } })
      return TabsModel.checkValue(data)
    }
  }

More info about models you can find in the corresponding md file.