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

@mohmmed_aariz/common

v1.0.2

Published

every module and every folder in a monorepo needs to have a package.json and tsconfig.json so bootstrap it accordingly

Downloads

1

Readme

every module and every folder in a monorepo needs to have a package.json and tsconfig.json so bootstrap it accordingly

now common folder contains modules that are used by both client and the server

here in our common folder we will write our zod types

// if you want to create a module and publish it to npm so other people can locally bring using npm install is by npmjs.org website. this is a registry where other people just put their code and allow others to use it

// rule of thumb:: when publishing into npm we don't publish typescript file. publishing ts file to npm means publishing your code to npm

changes in package.json : "name": "@mohmmed_aariz/common", "main": "dist/index.js",

to publish code

  1. npm login

  2. npm publish --access=public

  3. npm pack // to show what files you published ie. mohmmed_aariz-common-1.0.0.tgz we see a compressed file which shows what goes to npm here, we see that we have also published .ts file so we can stop uploading it by using .npmignore file same as .gitignore

  4. now we can run npm install @mohmmed_aariz/common in our repositiory then it will still work

// now to integrate it to our application we do npm install in both client and server

  • .d.ts is a declaration file it gives just the types of the code. not actual js code neither complete ts file which has both js and ts so to create it go to tsconfig.json and make declaration true here

now, dist has two files:: - .js and .d.ts here .d.ts just contain all the declaration and no js code which can be executed