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

create-crm-tmp

v1.0.3

Published

Créer un nouveau projet CRM basé sur le template

Readme

create-crm-tmp

Package npm pour créer un nouveau projet CRM basé sur le template.

🚀 Utilisation

pnpm create crm-tmp@latest mon-crm

📦 Workflow de mise à jour

Quand vous faites des modifications dans le projet crm-template, suivez ces étapes pour mettre à jour le package :

1. Synchroniser le template

# Dans le dossier create-crm-tmp
pnpm sync

Cette commande :

  • Copie tous les fichiers de ../crm-template vers template/
  • Exclut automatiquement les fichiers inutiles (node_modules, .next, .env, etc.)
  • Transforme le package.json pour le template

2. Incrémenter la version (optionnel)

Si vous voulez aussi incrémenter la version du package :

# Version patch (1.0.0 -> 1.0.1)
pnpm sync:patch

# Version minor (1.0.0 -> 1.1.0)
pnpm sync:minor

# Version major (1.0.0 -> 2.0.0)
pnpm sync:major

3. Tester localement (recommandé)

Avant de publier, testez le template :

# Dans un dossier temporaire
cd /tmp
pnpm create crm-tmp@file:../chemin/vers/create-crm-tmp test-crm

4. Publier sur npm

# Publier la nouvelle version
pnpm publish --access public

Note : Le script prepublishOnly s'exécute automatiquement avant la publication pour synchroniser le template.

📝 Scripts disponibles

  • pnpm sync - Synchroniser le template sans changer la version
  • pnpm sync:patch - Synchroniser et incrémenter la version patch
  • pnpm sync:minor - Synchroniser et incrémenter la version minor
  • pnpm sync:major - Synchroniser et incrémenter la version major
  • pnpm publish - Publier sur npm (synchronise automatiquement avant)

🔧 Fichiers exclus automatiquement

Le script exclut automatiquement :

  • node_modules/
  • .next/, dist/, build/
  • .env* (fichiers d'environnement)
  • pnpm-lock.yaml
  • *.tsbuildinfo
  • .git/, .vscode/, .idea/
  • generated/
  • Et autres fichiers de cache/build

📋 Checklist avant publication

  • [ ] Modifications faites dans crm-template
  • [ ] Exécuté pnpm sync ou pnpm sync:patch/minor/major
  • [ ] Vérifié les changements dans template/
  • [ ] Testé le template localement
  • [ ] Version mise à jour dans package.json
  • [ ] Prêt à publier avec pnpm publish