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

my-commands-jc

v1.6.1

Published

Permite crear archivos de programacion mediante comandos

Downloads

32

Readme

Installation

npm uninstall -g my-commands-jc && npm i -g my-commands-jc


Start vite project

jc vite init

Creating a component

jc g <componentName> <filePath>

Creating a interface

jc i <interfaceName> <filePath>


Start vite project with router

jc vite init --router

Creating App in router

jc g a <nameApp>

Creating App in router

jc g ap <nameApp>


Start express project

jc express-api init

npm i yargs npm i --save-dev @types/yargs

npm install chalk

import fs from "fs"; import path from "path"; import yargs from "yargs"; import chalk from 'chalk';

Ejecutando y mandando parametros

npm install --save-dev ts-node npx ts-node src/index.ts param1 param2

Publicando proyecto

npm adduser npm publish

Si hacemos un cambio debemos cambiar la version de lo contrario no dejara subir el paquete

"version": "1.1.0"

Luego publicamos

npm publish

Antes de ejecutar el npm publish, npm se fija en el package.json "prepare"

"prepare": "npm run build"

Creamos archivo .npmignore para indicar que archivos ignorar al subir a npm

.npmignore

npm install commander

Ejecutar mis pruebas

Ejecutando una prueba en la carpeta pruebas EXPRESS API

rm -rf pruebas && mkdir pruebas && cd pruebas npx ts-node ../src/index.ts express-api init

rm -rf ./* npx ts-node ../src/index.ts express-api init

rm -rf node_modules src package-lock.json postcss.config.js tailwind.config.js tsconfig.json vite.config.ts npx ts-node ../src/index.ts vite init --router