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

sam-and-his-friends

v6.0.0

Published

An express application extrac discourse data from renzhen1024.com

Downloads

3

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

taojstaojs

Keywords

Readme

Sam And His Friends

Build Status codecov License: MIT contributions welcome HitCount Maintainability

Set Up In Local Dev

  1. Requirements: Node V8.0+, Yarn, Redis V5.0+
  2. Checkout source code: $ git clone [email protected]:tningjs/sam-and-his-friends.git
  3. Install dependency: $ yarn install
  4. Start server: $ npm start
  5. Visit http://localhost:3000

How To Debug

  1. $: npm run debug
  2. Open Chrome, go to chrome://inspect/#devices
  3. Click "Inspect" in the Remote Target section (Notice: Cick the Node debug icon or click "Open dedicated DevTools for Node" not work for some version). This step should pause the process in the first line of source code, click continue in the debug tool.
  4. Open anther tab, go to localhost:3000, this step should pause the programm in the debugger; statement which you put in the code.

Chrome Debug

Deploy To Production

Auto deployment(CI) is configured using travis, the following is manual steps which similar to how CI is configured.

  1. Requirements: Node V8.0+, Yarn, Redis V5.0+, Process manager
  2. Checkout source code: $ git clone [email protected]:tningjs/sam-and-his-friends.git
  3. Install dependency: $ yarn install
  4. Build: $ npm run build
  5. Go to repository: $ cd <repository>
  6. Start server: $ NODE_ENV=production pm2 start ./server.js

To check logs, use $ pm2 logs.

Deploy A New Version To Production

  1. Find process ID by listing applications currently managed by PM2: $ pm2 list
  2. Stop an application: $ pm2 stop <app_name_or_id>
  3. Go to repository and build: $ cd <repository> && git pull && yarn install && npm run build
  4. Start application again $ NODE_ENV=production pm2 start ./server.js

Change log

The change log can be found on the Releases page.

Contributing

Everyone is welcome to contribute. Please take a moment to review the Contributing guidelines.

Authors and license

Tao Ning and contributors.

MIT License, see the included MIT-LICENSE.txt file.

Credits