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

dm-shared-api

v1.0.13

Published

A utility library to help make calls between dm microservices

Downloads

21

Readme

APi

The dm-shared-api is meant to be a sharable package to facilitate communication between microservices at DevMountain.

There are 2-3 points used in any shared-api:

  • The service - This is the endpoint that will be fullfilling the request
  • The middleman - This is the endpoint that will call our service from another server.
  • [Optional] the UI - Where appropriate a directive is made that knows how to invoke the middelman and inject functionality.

TheService

In the first use case we have two microservices that want to interact : class and surveys. class wants to be able to call surveys and embedd a directive to manage/invite students to take surveys.

In this use case surveys is our service because it will be fullfilling the end request.

class is going to be our middleman. The server on class will need an endpoint that can hit the service on surveys.

surveysDirective is our UI. It knows how to hit our middleman which then hits our service.

Usage

The service

If you want to fullfill an api request install this module then get your Routes construct.

var Routes = require('.').Routes;

Initialize a new route passing in your express app :

var routes = new Routes(app);

Invoke the desired route you wish to fullfill. This will add an endpoint to your express app for you ensuring each of the endpoints match to the rest of the app.

routes.Surveys.untakenSurveysByUsers(app);

The middle man

If you want to be a middleman and consume another service then follow the same steps as above for the service. For the last of the 3 steps look for an identically named function with then name Middleman appended. IE -

routes.Surveys.untakenSurveysByUsers(app);

->

routes.Surveys.untakenSurveysByUsersMiddleman(app);

UI

surveys Directive

Add a script reference to the surveysDirective.js file found in node_modules/dm-shared-api/lib/surveysDirective/surveysDirective.js to your product

Add dmSurveys as a dependency to your app

Required Middlemen

routes.Surveys.untakenSurveysByUsersMiddleman(app);

Adding new endpoints

Building

Only the the typesript files in the /src directory are compiled by webpack.
The rest are managed by the tsconfig.json file that can be passed into any typescript compiler.

Directive

The surveysDirective needs to be compiled with the webpack.config located in /src/surveysDirective

Testing

The directive can be tested by running the server.js file located in /lib with nodemon The navigate to /lib/test/surveysDirective/index.html

The service

The serivce is the actual endpoint that will be fullfilling the request. Most of our endpoints throughout our microservices are utilized only once by the product/service itself. But when an endpoint will be used more than once or needs to be used externally it should be included in this shared-api library.

  • Add an entry into the Routes.ts file located here.