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

update-copyright

v1.0.0

Published

Update a copyright statement with the current year. Also makes minor corrections.

Downloads

4,980

Readme

update-copyright NPM version NPM monthly downloads NPM total downloads Linux Build Status

Update a copyright statement with the current year. Also makes minor corrections.

Install

Install with npm:

$ npm install --save update-copyright

Usage

copyright(string, options);

Pass a string with a copyright statement to update, and it will be parsed and updated.

var copyright = require('update-copyright');

copyright('Copyright (c) 2015, Jon Schlinkert.');
//=> 'Copyright (c) 2015-2016, Jon Schlinkert.'

copyright('Copyright (c) 2012, 2015, Jon Schlinkert.');
//=> 'Copyright (c) 2012, 2015-2016, Jon Schlinkert.'

The current year is updated/appended to existing years. The rest of the information will stay the same unless new information is passed.

Lazy mode

If you're too lazy to pass anything at all, that's okay! You get a free copyright statement with the current year, using data from package.json!

copyright();
//=> 'Copyright (c) 2016, Jon Schlinkert.'

Optionally fills in author

Example

If the author is missing it will be filled in with the author from package.json.

copyright('Copyright (c) 2014.');
//=> 'Copyright (c) 2014-2015, Jon Schlinkert.'

Fixes Misspellings

It will use the author from package.json if a misspelling seems obvious (according to its Levenshtein distance):

copyright('Copyright (c) 2014, Jon Shlinert');
//=> 'Copyright (c) 2014, 2016, Jon Schlinkert.'

See the tests for more examples.

Options

A template is used to create the new copyright statement, and the options object is merged with the context that is passed to the template.

context

  1. The (context) object is populated with data from the parsed (old) copyright statement
  2. The object is then updated with the current year, author from package.json, and any other data you pass on the options.

Custom context

This is what the context object looks like. To override anything on the context just pass the property and value on the options:

{ year: '2015',
  prefix: 'Copyright',
  symbol: '(c)',
  template: '<%= prefix %><%= symbol ? (" " + symbol + " ") : "" %><%= years %>, <%= authors %>.',
  statement: 'Copyright (c) 2015, Jon Schlinkert',
  dateRange: '2014',
  latest: '2014',
  author: 'Jon Schlinkert' }

Example

Pass any custom data (as shown above) on the options:

copyright('Copyright (c) 2015.', {author: 'Foo Bar'});
//=> 'Copyright (c) 2015-2016, Foo Bar.'

About

Related projects

Contributing

Pull requests and stars are always welcome. For bugs and feature requests, please create an issue.

Contributors

| Commits | Contributor | | --- | --- | | 38 | jonschlinkert | | 1 | david-w-millar |

Building docs

(This project's readme.md is generated by verb, please don't edit the readme directly. Any changes to the readme must be made in the .verb.md readme template.)

To generate the readme, run the following command:

$ npm install -g verbose/verb#dev verb-generate-readme && verb

Running tests

Running and reviewing unit tests is a great way to get familiarized with a library and its API. You can install dependencies and run tests with the following command:

$ npm install && npm test

Author

Jon Schlinkert

License

Copyright © 2017, Jon Schlinkert. Released under the MIT License.


This file was generated by verb-generate-readme, v0.6.0, on June 26, 2017.