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

test_npm_sk_package

v1.0.2

Published

[![npm version](https://badge.fury.io/js/create-readme.svg)](https://npmjs.org/package/create-readme) [![downloads](https://img.shields.io/npm/dw/create-readme.svg)](https://npmjs.org/package/create-readme) [![open issues](https://img.shields.io/github/

Downloads

2

Readme

plugins installed

"@rollup/plugin-babel": "^6.0.4",

"@rollup/plugin-typescript": "^11.1.6",

"react": "^18.2.0",

"react-dom": "^18.2.0",

"rollup": "^4.12.0"

"tslib": "^2.6.2"

#main file should be linked from dist folder not ts file

#These are mandatory changes required before publish inside package.json

"main": "dist/index.js",

"types": "dist/index.d.ts",

#maintain version

"version":"2.0.0"

#to test locally use command

navigate to another project and type following command

npm link npm_package

after test un-link the library using following command:

npm unlink npm_package

last one should be name of package

#this will link this library to other projects and we can use locallay without install

to publish use command

npm publish

#Before publishing login into npm and then do it

to update readme file site:

https://stackedit.io/app#

all the file should be inside folder otherwise it wont work

create-readme

npm version downloads open issues license debug build status coverage status dependency status devDependency status Greenkeeper semantic release Gitter

Automatically creates README.md based on package.json and other existing files.

Usage

Configuration options can also be set in package.json's config.readme.

# API use

# Default options, explained in documentation
options = {
  debug: false
  silent: false
  encoding: 'utf-8'
  addDescription: ''
  addUsage: ''
  modules: ['CommonJS']
  unpkg: false
  licenseFile: 'LICENSE'
  badges: ['npm-version', 'travis', 'coveralls', 'dependencies', 'devDependencies', 'gitter']
  branch: 'master'
  replaceModuleReferences: true
  filename: 'README.md'
}

ReadmeCreator = require 'create-readme'
readmeCreator = new ReadmeCreator(options)
data = readmeCreator.parse()
content = readmeCreator.render data
readme = readmeCreator.write content
readme.catch (err) ->
  throw err
  process.exitCode = 1
readme-creator --encoding utf-8 --add-description "" --addUsage "" \
  --modules CommonJS --no-unpkg --license-file LICENSE.txt \
  --badges npm-version,travis,coveralls,dependencies,devDependencies,gitter \
  --branch master \
  README.md

Installation

Download node at nodejs.org and install it, if you haven't already.

npm install create-readme --save

This package is provided in these module formats:

  • CommonJS

Documentation

You can find a documentation here.

Dependencies

  • bluebird: Full featured Promises/A+ implementation with exceptionally good performance
  • commander: the complete solution for node.js command-line programs
  • debug: small debugging utility
  • github-url-to-object: Extract user, repo, and other interesting properties from GitHub URLs
  • mustache: Logic-less {{mustache}} templates with JavaScript
  • require-all:

Dev Dependencies

  • @lluis/codo: A CoffeeScript documentation generator.
  • @semantic-release/changelog: semantic-release plugin to create or update a changelog file
  • coffee-script: Unfancy JavaScript
  • coffeelint: Lint your CoffeeScript
  • coffeelint-no-mocha-only: This CoffeeLint plugin verifies there are no describe.only's or it.only's left in mocha tests
  • coffeelint-variable-scope: CoffeeLint rule that warn you when you accidentally overwrite outer scope variable
  • coveralls: takes json-cov output into stdin and POSTs to coveralls.io
  • ghooks: Simple git hooks
  • mock-fs: A configurable mock file system. You know, for testing.
  • nodemon: Simple monitor script for use during development of a node.js app.
  • npm-build-tools: Cross-platform command-line tools to help use npm as a build tool.
  • nsp: The Node Security (nodesecurity.io) command line interface
  • proxyquire: Proxies nodejs require in order to allow overriding dependencies during testing.
  • semantic-release: Automated semver compliant package publishing
  • test-coffee-module: run tests on .coffee files with sensible defaults
  • validate-commit-msg: Script to validate a commit message follows the conventional changelog standard

License

MIT