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

weskills-core

v0.0.57

Published

## Typescript module

Readme

WeSkills Core

Typescript module

  • yarn: run the yarn clean, then yarn lint, then yarn compile. Always use this.

  • yarn clean: clean the output folders ./es and ./js.

  • yarn lint: lint the ts files

  • yarn tsc: compile the TypeScript in ./ts into ES2015 in the ./es folder.

  • yarn babel: compile the ES2015 in the ./es into JavaScript in the ./js folder.

  • yarn compile: run both the tsc and the babel steps.

  • yarn test: run unit tests.

  • yarn watch: continuously run unit tests.

Comment versionner le Core

:warning: On ne fait une nouvelle version que sur master. C'est très important pour que le repo NPM et Git et tout le monde s'en sorte bien avec les tags de versions. :warning:

Pour créer une nouvelle version :

  • après un merge du core sur master, se mettre sur master (git checkout master), git fetch --all && git pull pour que la branche master locale soit bien à jour.
  • run la commande yarn version. Un petit prompt demande quelle version mettre, il faut respecter le Semantic Versioning sinon Yarn ne monte pas la version.
  • la commande yarn version peut prendre un argument comme --major, --minor, --patch pour incrémenter toute seule la version.
  • la commande pousse automatiquement le nouveau tag sur le Remote Git et met à jour le package.json. Rien à faire de plus.

Une fois que le pipeline Bitbucket du commit de la nouvelle version est passé, il faut aller sur la page du pipeline, et activer manuellement l'étape Publish qui va envoyer le nouveau Core sur le registry NPM.

Working with API and App locally

On the core repository :

  • yarn link

In App or API (if you want to add or update @weskills/weskills-core):

  • Go on the target repository (API and/or APP):
  • yarn link "@weskills/weskills-core"

Regénérer le token de connexion au registry delia

npm login --registry https://npm.weskills.com/ Username: admin Password: ******** Email: [email protected] cat ~/.npmrc

Mise à jour du core

  1. Après avoir merge la PR sur master, lancer: yarn version --patch || --minor || --major
  2. Lancer la pipeline pour déployer le core sur le registry Delia: https://bitbucket.org/delia-solutions/weskills-core/addon/pipelines/home#!