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

tms-customer-portal-api

v1.0.0

Published

Customer Portal API

Downloads

3

Readme

tms-customer-portal-api

Customer Portal API

Local development using Docker image of this service

To use this web service in your local Docker environment, add the following to docker-compose.yml:

  tms-customer-portal-api:
    image: 'casestack/tms-customer-portal-api:stage'
    ports:
      - '40407:40404'
    depends_on:
      - mongodb
    labels:
      - traefik.enable=false
    environment:
      - ENVIRONMENT=DEV
      - USER=vagrant

The Swagger UI should be available at http://home.devbox:40407/v1/_swagger, assuming the default Vagrant configuration is used.

Making changes to this service

To start making changes to this service, clone this repository and add the following entry to docker-compose.yml:

  tms-customer-portal-api:
    image: 'casestack/node-service:1'
    ports:
      - '40407:40404'
    depends_on:
      - mongodb
    labels:
      - traefik.enable=false
    environment:
      - ENVIRONMENT=DEV
      - USER=vagrant
    command: 'yarn start:dev'
    volumes:
      - >-
        /home/vagrant/casestack/<path to tms-customer-portal-api>:/opt/cs-service
      - '$HOME/.npmrc:/root/.npmrc'

Using the above configuration, the Swagger UI should be available at http://home.devbox:40407/v1/_swagger, assuming the default Vagrant configuration is used.

Security

Endpoints that start with /secure require an HTTP header api_key whose value is the JSON string that contains brokerageId and whatever else is required by that endpoint (perhaps customerId, shipperId, etc.). This helps avoid passing these as parameters to the endpoints via query strings or paths. See app/src/middleware/tsoa/authentication.ts for details of how security is done.

When using Swagger UI, click on the red icon with exclamation point ! to enter the JSON string. An example JSON string is:

{
    "brokerageId": "brokerage id value"
}

Build process

The app uses koa with routes to controllers auto-generated from TypeScript's decorators in the *Controller class. The routes are generated by tsoa according to the template app/src/routes/koa-template/routes.txt.

After the build, swagger.json is also auto-generated by tsoa. The JSON is transformed to YAML by json2yaml for Swagger UI.

The file tsoa/v1.json defines how tsoa should generate the routes.ts and swagger.json.

VS Code config

Prettier and imports sorting

  "editor.formatOnSave": true,
  "editor.codeActionsOnSave": {
    "source.organizeImports": true
  }