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

@wazzifa/common

v1.0.21

Published

1- extract authentication related login into separate dependency --------------------------------------------------------------- you have 3 ways: 1- Copy/Paste --> Worst option 2- GIT sub module 3- Publish common code as npm package registery 4- We have a

Downloads

4

Readme

1- extract authentication related login into separate dependency

you have 3 ways: 1- Copy/Paste --> Worst option 2- GIT sub module 3- Publish common code as npm package registery 4- We have again 3 options: - Public npm - *Organization (public / private) - Self hosted npm server. 5- Let's create new project called common (npm init -y) 6- You must have your common library committed into git repos (init, add, commit) 7- Publish the package using (npm publish --access public)

To make our common libraries agnostic and work with any porject (type script, or java script) we we will write our library in type script but publish it as java script. to do so follow these steps: 1- tsc --init (create tsconfig.json file) 2- install type script (npm install typescript del-cli --save-dev) 3- transpile the type script to java script:

  • in application.config -- scripts sections -- add build command, and clean -- and modify tscconfig.json to let tsc know where is the code is uncomment declaration uncomment outDir and make it "./build" 4- when you import from the module the main config determines what file to be loaded, we need to make sure it is the index.js located in the build folder not src. add also (after the main config), the "types" : "./build/index.s.ts" wat is the main type defintion "files" : "./build/**/*" everything in build what set of files we wnat to make sure it must be included in publish