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

@mdex/backend-sdk

v0.0.27

Published

Used for coding sharing between repository for project `MDEX`

Downloads

5

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

mdexmdex

Keywords

Readme

@mdex/backend-sdk

Used for coding sharing between repository for project MDEX

Respository that will use package

Types of files being shared

Constant (@mdex/backend-sdk/lib/constant)
Decorators (@mdex/backend-sdk/lib/decorators)
Dto (@mdex/backend-sdk/lib/dtos)
Exceptions (@mdex/backend-sdk/lib/exceptions)
Middlewares (@mdex/backend-sdk/lib/middlewares)
NestService (@mdex/backend-sdk/lib/nestService)
Utils (@mdex/backend-sdk/lib/utils)

What should not be included in this repository

If one or more of the following is available in the file being considered then the file SHOULD NOT be added it to @mdex/backend-sdk (can be discussed over):

  • File relies on local environment. For example, config.production.ts .env

How to add files to this repo

  1. add files as normal but also add index.ts that export constants or functions correctly. For example, anyone importing @mdex/backend-sdk/lib/constant will be able to get all constants from the constants folders
  2. use yarn build on your local and try if you can import the files (from dist folder) properly. NOTE: Make sure to use absolute path as derived path @utils/.. might create issues after package is being published
  3. before creating release branch, use bumpVersion:release:dry to confirm the version you are bumping up to.
  4. create release branch on github based on the version obtained from Step 3 and the npm package vX.X.X-beta.X should be published based on the version seen in Step 3.
  5. Try importing the npm package in Step 4 in your repository and test out until satisfactory. If you need to make adjustment, then just directly create a new branch from release branch and merge it to publish the new beta npm package for testing.
  6. Once the update is satisfactory, then merge release branch to master to create official npm package vX.X.X, and then merge master branch back to development branch

Things to Note:

  • Once a npm package is published, you cannot overwrite that npm package. For example, you cannot publish v1.1.0-beta.0 if this number has been published previously.