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

@eco8200/data-models

v19.0.1-minor-strapi-bridging.21

Published

DTOs for gsharim system

Downloads

67

Readme

Data Models NPM Package 🌉

DTOs package for gsharim system, backend & frontend!

Installation

Run the following command:

npm install @eco8200/data-models

Development

For each update of the codebase, you should open a new branch containing one of the following prefixes:

- major-*
- minor-*
- patch-*

This is critical for our CI/CD automations. Choose the prefix that best fits your changes:

  • major - for big updates (like new DTOs for a new feature, API breaks, large bug fixes)
  • minor - for small updates (for example, new optional fields in a specific DTO)
  • patch - for bugfixes (fixing a DTO that doesn't fit the current scheme/usage, typos in field names and so on)

All the branches should be checked out from dev only! After merging to dev, the automation will automatically create a PR to the master branch. Only after this PR will be merge then the package will be published in it's stable form.

Documentation Reference

Find the scheme plannings in this draw.io diagram :)