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

magic-service

v1.0.1

Published

a simple startup project written in ts (based on gulu 2.0)

Downloads

2

Readme

Developing & Debugging

Quickly starting up the development server from the command line

$ npm run dev

The project template has built-in VSCode debugging configuration, and if you need breakpoint debugging, you can also start the application through VSCode's launcher.

Debugger

Service Discovery Switch

The template has a built-in BOE environment ROUTE_IP by default. If you need to switch it, you need to modify the start script of the package.json

You can chang the environment variable ROUTE_IP to switch between different environments. I.e. ROUTE_IP=x.x.x.x. The value is the IP of the corresponding machine room.

For example, GULU_ENV=dev ROUTE_IP=10.225.84.22 nodemon bootstrap.js, of which 10.225.84.22 is an instance of the Boe environment. Then the service will start under the BOE environment.

How to get the IP address of the BOE environment

  • Use the IP of devbox (you need to execute sudo /opt/tiger/consul_devbox/bin/switch.sh boe first to switch consul to BOE environment)
  • Use the IP of TCE BOE instance

How to get the IP address of the online environment

  • Use the IP of devbox (you need to execute sudo /opt/tiger/consul_devbox/bin/switch.sh langfang first to switch consul to BOE environment)
  • Use the IP of TCE BOE instance

Setting ROUTE_IP Not Working

Check whether the following environment variables exist in the system, and if so, delete the corresponding environment variables or modify them to the value of ROUTE_IP

  • CONSUL_HTTP_HOST
  • MY_HOST_IP
  • TCE_HOST_IP