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

@carlostkd7/m3

v2.0.1

Published

m3 is a small microservice wrapper, based on **express**, **redis**, **jwt**, and **socket.io**.

Downloads

57

Readme

m3_codebase

Microservice deploy library

m3 is a small microservice wrapper, based on express, redis, jwt, and socket.io.

Let's see how to use:

  • Install wih npm i @carlostkd7/m3
  • Create a script, i.e. builder.js:

builder.js:


var ms = require("@carlostkd7/m3");

ms.build( {service: "supertest",init : true} ).then(function(){
	 ms.apify()
});

In the above example, the microservice name is supertest.

  • To run the script with node or, if you prefer, nodemon, just do a
$ nodemon builder.js
  • If this is your first time running the build option, a folder with same name as your microservice (supertest for me) will be created as follows with an entire example app:
-- package.json
-- builder.js

#this is your new microservice structure:
-- supertest/
	-- .env
	-- app.js
	-- io.js
	-- modules.js
	-- www/
		-- index.html
		-- main.js
  • The process will create an example api that you can just start to code, at supertest/app.js and supertest/io.js you can put all your endpoints and socket.io actions, and import all your required modules inside supertest/modules.js

  • This structure will help you to have a clean app.js and io.js files, without the pain of doing lots of imports on each file, just put your module calls inside the modules.js script and it will be available at inn.modules.ms object.

  • After your first launch the builder.js on command line, nodemon, npm etc., you will be able to test your application on localhost:3000, and a simple web chatroom will be shown.

  • If you don't provide any ssl keys (server.key and server.cert files), the server will start with http, otherwise, it will launch your app under https.

  • The API already have a jwt authentication middleware, and a simple rule is required here: any endpoint that includes "auth" on it's url requires a valid headers authorization token. If you require open endpoints, don't use the auth prefix on them.

  • it also supports two database engines (mysql and mongodb under mongoose), both of them located on inn.connections.

You can customize all your app needs inside .env file, we are also providing a sample with all required variables

I recomend to use nodemon for testing and dev, it is already on dependencies.

Next step is to automate the dockerization app process.

Regards!