Giter Club home page Giter Club logo

create-readme's Introduction

Limited maintenance

This repository is in limited maintenance mode. Please consider migrating to jsx-readme.

create-readme

npm version downloads open issues license debug build status coverage status dependency status devDependency status 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

create-readme's People

Contributors

dbartholomae avatar dependabot[bot] avatar greenkeeper[bot] avatar

Stargazers

 avatar

Watchers

 avatar  avatar  avatar

create-readme's Issues

An in-range update of semantic-release is breaking the build 🚨

The devDependency semantic-release was updated from 15.12.4 to 15.12.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v15.12.5

15.12.5 (2018-12-11)

Bug Fixes

  • allow to set ci option via API and config file (862ec4c)
Commits

The new version differs by 8 commits.

  • 649b530 docs: mention that debug option is CLI only
  • 862ec4c fix: allow to set ci option via API and config file
  • 6b110b6 docs: switch to spectrum.chat
  • e4c6649 docs: syntax fixes in plugins list
  • 6220641 docs: add @semantic-release/apm to plugins list
  • a45273e docs: add maven-semantic-release to list of community plugins
  • d109113 chore(package): update nyc and sinon
  • cd69583 test: delete unused test helper file

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

An in-range update of nodemon is breaking the build 🚨

The devDependency nodemon was updated from 1.18.5 to 1.18.6.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

nodemon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v1.18.6

1.18.6 (2018-11-05)

Bug Fixes

Commits

The new version differs by 1 commits.

  • 521eb1e fix: restart on change for non-default signals (#1409) (#1430)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of semantic-release is breaking the build 🚨

The devDependency semantic-release was updated from 15.12.0 to 15.12.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v15.12.1

15.12.1 (2018-11-21)

Bug Fixes

  • push only tags to remote repo (2b082ac)
Commits

The new version differs by 10 commits.

  • 2b082ac fix: push only tags to remote repo
  • aa022e0 test: clarify variables name
  • f2ede5b docs: typo in JS docs
  • 9742712 test: verify errors have message and details
  • 5937f13 test: fix typo
  • 43dbd10 refactor: prefer filter shorter form
  • 9f5645c refactor: harmonize git utils function names
  • e594638 test: prefer array spread
  • 244f014 docs: add Codefresh in list of CIs with pipelines
  • 218d830 docs: fix quote marks (#986)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.