npm-expansions
Advanced tools
Comparing version 1.14.0 to 2.0.0
{ | ||
"name": "npm-expansions", | ||
"version": "1.14.0", | ||
"description": "What does n-p-m stand for?", | ||
"main": "index.json", | ||
"repository": { | ||
"type": "git", | ||
"url": "https://github.com/npm/npm-expansions" | ||
"version": "2.0.0", | ||
"author": "Zeke Sikelianos <zeke@sikelianos.com> (http://zeke.sikelianos.com/)", | ||
"bugs": { | ||
"url": "https://github.com/npm/npm-expansions/issues" | ||
}, | ||
"devDependencies": { | ||
"tap": "^0.4.13" | ||
}, | ||
"homepage": "https://github.com/npm/npm-expansions", | ||
"keywords": [ | ||
"npm", | ||
"abbreviations", | ||
"acronym", | ||
"abbreviations", | ||
"names", | ||
"naming-is-hard", | ||
"npm", | ||
"recursive-bacronymic-abbreviations" | ||
], | ||
"author": "Zeke Sikelianos <zeke@sikelianos.com> (http://zeke.sikelianos.com/)", | ||
"license": "ISC", | ||
"bugs": { | ||
"url": "https://github.com/npm/npm-expansions/issues" | ||
"main": "expansions.js", | ||
"repository": { | ||
"type": "git", | ||
"url": "https://github.com/npm/npm-expansions" | ||
}, | ||
"homepage": "https://github.com/npm/npm-expansions", | ||
"scripts": { | ||
"alphabetize": "./bin/alphabetize.js", | ||
"a": "npm run alphabetize", | ||
"prepublish": "npm run alphabetize" | ||
"prepublish": "npm test", | ||
"test": "tap test" | ||
}, | ||
"browser": { | ||
"fs": "brfs" | ||
} | ||
} |
# npm-expansions | ||
[![Build Status](http://img.shields.io/travis/npm/npm-expansions.svg?style=flat-square)](https://travis-ci.org/npm/npm-expansions) [![NPM version](http://img.shields.io/npm/v/npm-expansions.svg?style=flat-square)](https://www.npmjs.org/package/npm-expansions) [![NPM license](http://img.shields.io/npm/l/npm-expansions.svg?style=flat-square)](https://www.npmjs.org/package/npm-expansions) | ||
What does n-p-m stand for? | ||
## What | ||
## What This Is | ||
An array of expansions, like: | ||
This is the source code for the three-word thingies that randomly appear in the header of the [npmjs.com](https://npmjs.com) website. Examples include: | ||
- Napping Panda Missionaries | ||
- Never Poke Monkeys | ||
- Node Package Manager | ||
- nom, please more | ||
- Naughty Push Message | ||
- Nectar of the Programming Masses | ||
- Needless Pachouli Manufacture | ||
- Neil Patrick's Mansion | ||
- Never Program Mad | ||
- Never Push to Master | ||
- Neverending Plethora of Modules | ||
- Newton's Programmatic Measurements | ||
- Newts Parading Majestically | ||
- Nice Poodle, Mister | ||
- Nickel Plated Moose | ||
- Nineties Party Mix | ||
- Null Pointer Missing | ||
- Nymphets Playing Mahjong | ||
## How | ||
## How to Contribute | ||
```sh | ||
npm install npm-expansions --save | ||
``` | ||
Add your own expansion to [index.txt](index.txt), then send us a pull request! If you think of multiple possibilities, it's best to submit them as separate PRs, as we may like some but not others. | ||
## Contributing | ||
Some other suggestions: | ||
Just submit a pull request adding an expansion to the list! If you think of multiple possibilities, it's best to submit them as separate PRs, as we may like some but not others. | ||
- be meaningful. Three random words is not good enough. | ||
- be funny. This is very subjective, we realize, so try not to take it personally if we don't get it. | ||
- be novel. If your expansion starts with "No", "New", "Never" or "Node" the other two words better be pretty great. | ||
- avoid hyphenation, especially "non-". Yes, there are some in there already. Sorry. | ||
- use actual words. You can't just make up random new words. Unless they're really good. | ||
- Avoid names of people and products (other than npm ;-)) | ||
- avoid anything that even slightly hints of violating npm's [code of conduct](https://www.npmjs.com/policies/conduct/). These are literally the first words that appear on the website, and our audience is very broad, so it's best to avoid things that can be misconstrued. |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 1 instance in 1 package
10249
7
38
1
12