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

porta-v3

v1.2.2

Published

Porta v3 API.

Downloads

9

Readme

porta-v3

Date 2021/12/27

Stores and Retrieves Log and Result Data for PortaMetrics

Getting started for developers

  1. Copy porta-v3.env from \motionmetrics.net\i2l\Bamboo_Files\MMPro_Env\I2L-Staging and rename it as .env

  2. Copy .npmrc from \motionmetrics.net\i2l\Bamboo_Files\MMPro_Env\I2L-Staging

  3. Install all the dependencies with the command:

    npm ci
  1. Verify Segmentation-Service-Python is running locally or as a Docker container at localhost:7199/fmsegmentation/v2/help

  2. Run Unit test

    npm test
  1. Compile the typescript to javascript and run lint
    npm run-script build
  1. Start the program
    npm start

Running Integration Tests

  1. Copy the npm-qc-user-credentials.env from NAS, and save it to the IntegrationTest folder and rename it as .env

  2. Change ROOT_DOMAIN to point to http://localhost:8080, if you are testing it locally.

  3. Repeat Steps in "Getting started for developer" if you haven't done

  4. Run the Integration Test:

    npm run-script integration-test

Run Docker

  1. Run the docker command
docker run -it --name "porta-v3" --network host porta-v3

Commit Message Format - Angular Convention

(): │ │ │ │ │ └─⫸ Summary in present tense. Not capitalized. No period at the end. │ │ │ └─⫸ Commit Scope: animations|bazel|benchpress|common|compiler|compiler-cli|core| │ elements|forms|http|language-service|localize|platform-browser| │ platform-browser-dynamic|platform-server|router|service-worker| │ upgrade|zone.js|packaging|changelog|docs-infra|migrations| │ devtools │ └─⫸ Commit Type: build|ci|docs|feat|fix|perf|refactor|test see https://github.com/angular/angular/blob/main/CONTRIBUTING.md#-commit-message-format for more details

Alternatively, you can use the module commitizen to help you format the commit message.

  1. install commitizen
    npm install -g commitizen
  1. making your repo commitizen-friendly
    commitizen init cz-conventional-changelog --save-dev --save-exact
  1. commit your changes Simply use git cz or just cz instead of git commit when committing. You can also use git-cz, which is an alias for cz.
    git add .
    git cz

see https://github.com/commitizen/cz-cli for more details

Updating API Doc

  1. Grab the porta-v3.json from mm-staging-openapi-definitions S3 bucket in motionmetrics-dev account

  2. Update JSON accordingly

  3. Ensure metadata is configured correctly under property

{
  Type: User defined,
  Key: x-amz-meta-apidoc-access,
  Value: edit
}
  1. Upload the updated JSON to mm-staging-openapi-definitions in motionmetrics-dev account
  2. Upload the same JSON to mm-prod-openapi-definitions in motionmetrics-prod account

Note:

We are currently using Node LTS v16.13.0