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 🙏

© 2026 – Pkg Stats / Ryan Hefner

my-nutri

v2.79.2

Published

MyNutri backend project

Readme

codecov-b

MyNutri

Nutrição nunca foi tão fácil

Getting Started

Setup

M1 machines

Hasura Configure

  • If needs to change default configuration for Hasura (ports, admin secret, etc..), duplicate .env.example file and rename it for .env.
  • Done, just change the configurations.

Run

  • yarn start: Start Hasura and serverless.
  • yarn hasura:up: Start Hasura Docker container.
  • yarn hasura:start: Start Hasura and apply metadata and migrations.
  • yarn hasura:stop: Stop Hasura.
  • yarn hasura:console: Open Hasura Console.
  • yarn backend:start: Start serverless functions.
  • yarn backend:deploy: Deploy serverless functions.

Cli

The commands will available only on serverless/users folder.

  • [ENV=stag] yarn console [command] [args]. Ex.: yarn console patients updateExtraData '2022-05-01' '2022-06-01'

Hasura

All config files, metadata and migrations created are in ./hasura folder. Current version is:

  • v2.2.0

Serverless

The serverless functions are in ./serverless folder separated by microservice:

  • users: for now, there are only microservice with all project functions.

Libs Folder

When has a big size 3-party library its added in ./libs folder with package.json configured for to be possible shared with serverless functions and also created a specific serverless layers for it.

Heroku

Manual Deploy

Uses when has a new Hasura version:

  • git push heroku master

Commit Messages

Git Commit Guidelines

Follow The seven rules of a great Git commit message (TL;DR)

  1. Separate subject from body with a blank line
  2. Limit the subject line to 50 characters
  3. Capitalize the subject line
  4. Do not end the subject line with a period
  5. Use the imperative mood in the subject line
  6. Wrap the body at 72 characters
  7. Use the body to explain what and why vs. how

Commit Types

As configured on .commitlintrc.yml, it must be one of the following:

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • ref: A code change that neither fixes a bug nor adds a feature
  • test: Adding missing tests or correcting existing tests
  • revert: A commit that reverts a previous commit
  • chore: Changes to the build process or auxiliary tools and libraries such as documentation generation
  • ci: Changes to our CI configuration files and scripts (example scopes: Circle, BrowserStack, SauceLabs)
  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • perf: A code change that improves performance
  • git: Changes on git files, such as .gitignore

Commit Best Practices

  • Commit often
  • Keep commits small and atomic
  • Write S.O.L.I.D. commits
  • Write meaningful titles targeting for non-technical readers
  • Write commits that would help the Code Review
  • Add any extra information that would help the Code Review
  • Reference the issue that originated the commit

References

  • Hasura - Get realtime GraphQL APIs instantly
  • Migrations - Migrations for a new database and Hasura instance
  • PostgreSQL - The World's Most Advanced Open Source Relational Database
  • NestJs - A progressive Node.js framework for building efficient, reliable and scalable server-side applications.
  • NestJs-Console - A ready to use service class for your modules that exposes methods to register commands and sub commands using commander
  • Serverless - Provide full serverless application lifecycle management.
  • Rollbar - Rollbar provides real-time exception reporting and continuous deployment monitoring for developers
  • Jest - Javascript Testing Framework with a focus on simplicity
  • Faker - Generate massive amounts of fake (but realistic) data for testing and development.
  • FactoryBot - A factory library for Node.js