I see ~10 pumpkin-themed 'npm texts' on the live site, and wanted to add more, but noticed that expansions.txt only has 3 pumpkin texts. Where are the other pumpkins coming from?

So, I made a little node module for all of the example corpora used by NLTK, which includes basically these books: ['austen-emma.txt', 'austen-persuasion.txt', 'austen-sense.txt', 'bible-kjv.txt', 'blake-poems.txt', 'bryant-stories.txt', 'burgess-busterbrown.txt', 'carroll-alice.txt', 'chesterton-ball.txt', 'chesterton-brown.txt', 'chesterton-thursday.txt', 'edgeworth-parents.txt', 'melville-moby_dick.txt', 'milton-paradise.txt', 'shakespeare-caesar.txt', 'shakespeare-hamlet.txt', 'shakespeare-macbeth.txt', 'whitman-leaves.txt']

I then made a module that basically automatically goes through them looking for 'npm' acronyms. I got these:

[ 'not promoted Mr',
  'not produce much',
  'no positive merit',
  'not persuade myself',
  'next perhaps Mr',
  'not pity me',
  'not pity me',
  'nearly promised moreover',
  'not prevent my',
  'not pin myself',
  'not prevent MY',
  'No Pall Mall',
  'not performed my',
  'not pardon my',
  'not poured me',
  'now put me',
  'now persuade men',
  'new paradise Michael',
  'necktie Put me',
  'new psychometric method',
  'not pull my',
  'NEW playthings mother',
  'now pray Mrs',
  'not particularly melodious',
  'no pocket money',
  'never pinch my',
  'noble prophet Moses',
  'no possible mistake',
  'no Paradise myself',
  'nothing profits more',
  'next Provokes my',
  'now pleases more',
  'not Pompey many',
  'not Parchment made',
  'nor Poyson Mallice',
  'Non pareill Mur',
  'not press my',
  'not prove me' ]

My question now is -- what do you think? Are these worth adding? Should I make it a node package?

Not a serious issue.

It doesn't seem like many of the recent expansions are live at npmjs.com. Not sure if this is purposeful, a caching issue, or I'm just being dumb.

On the live site, this file appears to contain the expansions: https://www.npmjs.com/static/js/index.min.6833b586.js.

However, those expansions do not match the latest expansions.txt file.

Nirvana Plateau MP3

As a curiosity I made a program to compute all npm palindromes:

nam pap man
nam peep man
nam pep man
nam pip man
nam poop man
nam pop man
nam pullup man
nam pup man
name pape man
name pe man
name peepe man
name pipe man
name pope man
namer pre man
nametape pate man
namma pam man
nams paps man
nams peeps man
nams peps man
nams pips man
nams poops man
nams pops man
nams pullups man
nams pups man
namu pupu man
ne psi mispen
nema pa men
nema palapa men
nema papa men
nema pipa men
nema pupa men
nemesia paise men
nitramine peni martin
no pote metopon
nom pap mon
nom peep mon
nom pep mon
nom pip mon
nom poop mon
nom pop mon
nom pullup mon
nom pup mon
noma pa mon
noma palapa mon
noma papa mon
noma pipa mon
noma pupa mon
nome pape mon
nome pe mon
nome peepe mon
nome pipe mon
nome pope mon
nomograph pargo mon
noms paps mon
noms peeps mon
noms peps mon
noms pips mon
noms poops mon
noms pops mon
noms pullups mon
noms pups mon
nongame pape magnon
nongame pe magnon
nongame peepe magnon
nongame pipe magnon
nongame pope magnon
notum pap muton
notum peep muton
notum pep muton
notum pip muton
notum poop muton
notum pop muton
notum pullup muton
notum pup muton
noumena pane muon
noumenal peneplane muon
noumenal plane muon

Unfortunately quite a few end up being scatalogical due to the p in the middle (nom poop mon...) Still, there might be a few here that are almost sensible enough to approach something clever.

Even if it doesn't make the cut, perhaps you might find them amusing.

When the expansions link on the site is clicked it becomes blue underlined until something else is clicked on. (until unselected)

Just so you guys know.

PR => #2067

This is the error I am getting when i try to build the package.
Fetching packages...
{ Error: unexpected end of file
at Zlib._handle.onerror (zlib.js:371:17) errno: -5, code: 'Z_BUF_ERROR' }

node --version
v6.15.1

const regex = /^[nN]\S+ [pP]\S+ [mM]\S+$/msg;

Does something like 'Nevertheless Published Mine' make sense in English?

I realize that this starts with never, but that is why I made an issue instead of a pull.

"Norse Power Metal" is doubled.
This might be intentional... If so:
"Nope! Preciously Meticulous."

Getting below error when trying to push new branch however I'm able to pull the code.
"remote: Permission to npm/npm-expansions.git denied.
fatal: unable to access 'https://github.com/npm/npm-expansions.git/': The requested URL returned error: 403"

It appears that no PR has been merged for several months now.

I think either PRs should be merged again (perhaps consider removing old quotes in favor of new ones?) or the website should stop redirecting to this repo.

Thoughts?

I've forgot pwd, after taking the link couldn't login. is it normal :) ?

PR => #2345

On executing the command npm test. I get the following error

> [email protected] pretest /Users/karthicksubramanianm/codei/npm-expansions
> node build.js


> [email protected] test /Users/karthicksubramanianm/codei/npm-expansions
> tap test

sh: tap: command not found
npm ERR! Test failed.  See above for more details.

System Information:

OS: Mac High Sierra
node: 10.8.0
npm: 6.2.0

Neat Pancake Maker

Line number 791 and 792 are mirrored not sure if it was meant to be that way or a mistake just wanted to give a heads up. Also it might look weird on npm website.

nuǝɯ pǝɥsᴉꞁod mǝu
nuǝW pǝuoᴉʇᴉsoԀ ʎlǝʌᴉʇɐƃǝN

Here is the shortest single javascript expression I could find to generate npm expansions:

require("fs").readFileSync("/usr/share/dict/british-english",{encoding:'utf8'}).split('\n').reduce(function(p,c){o={'n':0,'p':1,'m':2};if(Math.random()<.1)p[o[c[0]]]=c;return p},[]).join(' ');

Can someone make it shorter?

Nice People Manifestation

how to Configure scripts in package.json (a) to check the versions of npm and node by using npm run release | tee output1.txt (b) to execute index.js by using npm run build | tee output.txt ?????

The pull requests were starting to pile up (130+) and many of them were not green-button mergeable, so I wrote this little bash function:

yolo() {
  set +x
  git checkout -b $1-$2 master
  git pull https://github.com/$1/npm-expansions.git $2
  git add .
  git commit -am "yolo"
  git checkout master
  git merge --no-ff $1-$2
  git push origin master
  set -x
}

Then I pulled down all the user:branch name pairs from the github API using curl and the indispensable json CLI module:

curl -s "https://api.github.com/repos/npm/npm-expansions/pulls?sort_created&direction=asc&per_page=100&page=1" \
  | json -a head.label \
  | pbcopy

Then I hand-prepared a list in Atom:

yolo sudodoki npm-expansions-duh
yolo brentertz patch-2
yolo andela-bojengwa patch-1
...

Once every PR had been merged, I cleaned up all the merge conflicts and threw out expansions.json. Now there's a simple index.js that ingests the text file and splits by line. There is no build step, and brfs is used to make the fs call work in the browser.

As of this moment, we're at 99 contributors. Keep those expansions coming, and enjoy the simpler new format: txt

<3

I don't mean to be rude, but I looked at the amount of pull requests open, and there is quite a lot!
I kindly respect the fact it takes time to look through, as of writing, 238 pull requests, although I would be happy to, at some point, look though some of the pull requests.

Don't we have enough trouble getting women to work in this industry already?

......................

The sentence "Noodles, Poodles and More!" appears 2 times in the expansions file at line 639 and 640.

PR => #2068

I know it's against the rules but I had to say it 🤣

The README instructions suggest to "Avoid expansions that are gendered, sexual, aggressive, or violent. We are a diverse, positive place." This is really awesome and totally expected w/ NPM. However, quite a few of the expansions violate this, e.g. from the README file itself:

Nymphets Playing Mahjong

Where Wikipedia defines a "Nymphet" as "a sexually attractive girl, or young woman". Suggest cleaning up some of the more questionable expansions to make the list more in line with the instructions and Code of Conduct.

Can we add an Spanish one ?

Nueva Página Multimedia (translation: New Multimedia Site)

I have npm installed in my machine. But not able to install module ngeohash via npm. Please find the error message below. Any help will be appreciated.
npm -v
6.5.0

npm install ngeohash

[email protected] install /Users/babu.yadav/repo/devices_api_node/node_modules/ngeohash
browserify . -o ngeohash.js -s ngeohash

sh: browserify: command not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] install: browserify . -o ngeohash.js -s ngeohash
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/babu.yadav/.npm/_logs/2018-12-16T09_35_23_786Z-debug.log

This is a cool thing, but isn't the overhead of a whole pull request for a single line a bit too much? I mean, it's not very optimized for this use-case.

I thought about contributing something ("next package, maybe" and "neurotic programmers' medicine"), then read that you need a whole pull request and thought... that's a lot of work for a suggestion system.

So, hopefully not sounding like a lazy ass, wouldn't issues be more lightweight? Someone responsible could just go through them once in a while and close them while adding.

What / Why

why does the word "naM ,sevitcepsreP weN" is accepted as the meaning of n-p-m in the expansions file?

I am opening this issue because:

• npm is crashing
• npm is producing a incorrect install
• npm is doing something I don't understand
• Other (see below for feature requests)

What's going wrong?

This issue has been happening since 2.2.4 I was doing npm test on npm expansions and it keeps failing.
Here is my complete log about the test

> [email protected] pretest C:\Users\Jerome\node_modules\npm-expansions
> node build.js


> [email protected] test C:\Users\Jerome\node_modules\npm-expansions
> tap test

internal/modules/cjs/loader.js:583
    throw err;
    ^

Error: Cannot find module 'tap'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
    at Function.Module._load (internal/modules/cjs/loader.js:507:25)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:20:18)
    at Object.<anonymous> (C:\Users\Jerome\node_modules\npm-expansions\test\index.js:2:12)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)
test/index.js ......................................... 0/1
  not ok test/index.js
    timeout: 30000
    file: test/index.js
    command: 'C:\Program Files\nodejs\node.exe'
    args:
      - test/index.js
    stdio:
      - 0
      - pipe
      - 2
    cwd: 'C:\Users\Jerome\node_modules\npm-expansions'
    exitCode: 1

total ................................................. 0/1


  0 passing (161.476ms)
  1 failing

npm ERR! Test failed.  See above for more details.

How to reproduce the problem

Install tap and npm-expansions then

cd node_modules
cd npm-expansions
npm test

Supporting information

• npm config get registry prints https://registry.npmjs.org
• npm -v prints 6.4.1
• node -v prints v10,11,0
• OS: Windows
• Network issues: None
• Location where npm was run: US
  • I use a proxy to connect to the npm registry
  • I use a proxy to connect to the web
  • I use a proxy when downloading a Git repos
  • I access the npm registry via a VPN
  • I don't use a proxy, but have limited or unreliable internet acess
• Container:
  • I develop using Vagrant on Windows
  • I develop using Vagrant on OS X or Linux
  • I develop / deploy using Docker
  • I develop to a PaaS (Triton, Heroku)

I want to contribute the repository so i forked and cloned it, and also made my changes to the extensions.txt file.
It was written in How to Contribute to run npm test, but i get the following error when i run npm test:

PS C:\Users\Muktadir Khan\Downloads\Opensource\npm-extensions> npm test
npm ERR! path C:\Users\Muktadir Khan\Downloads\Opensource\npm-extensions\package.json
npm ERR! code ENOENT
npm ERR! errno -4058
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open 'C:\Users\Muktadir Khan\Downloads\Opensource\npm-extensions\package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent 

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Muktadir Khan\AppData\Roaming\npm-cache\_logs\2019-10-05T13_43_41_667Z-debug.log

Please guide as to what am i doing wrong.

@seldo @zeke
Basically echoing #1632
It looks like this repo has been pretty inactive since mid 2018, I'm just wondering if it's still being maintained?
Otherwise it probably shouldn't be linked to https://www.npmjs.com/. Maybe, you can use a bot to maintain this repo instead? I don't imagine that being exceptionally difficult, and would make this repo a lot more useful. I could implement one, if you guys want.

I have submitted 100+ expansions, but only 2 of them have been merged. I noticed that only a few contributed expansions get merged each month, and you use a LIFO (Last In, First Out) system, which means the people who contributed first are being overlooked by the newest contributions.

For example, I have one expansion: Narnia's Psychedelic Mushrooms that I submitted 29 days ago, but just the other day you merged a similar expansion: Neolithic Psychedelic Mushrooms that was submitted 4 days ago, so naturally I feel like mine won't be merged now, because it is now too similar to an existing expansion, even though mine was submitted 25 days earlier. So a FIFO (First In, First Out) system keeps everything balanced, and fair.

It is really fun to participate in this expansions repo, and see our contributions on the npm site, which we use everyday, but lately our contributions aren't really being added (only a couple each month). So I propose that you merge your pull requests using a First In, First Out system, so the earliest contributors get proper credit, and aren't lost to oblivion.

Lastly, if you need some help, I am happy to help you do the grunt work. Even with 100+ contributions, I am still yet to see any of my expansions on the npm website, and it is, after all, a dream of mine to see my contribution shining in the top-left corner of the npm website I use everyday. 😃 ❤️

PR => #2069

Steps to Reproduce

Run npm install after cloning the repo

> npm install
npm WARN prepublish-on-install As of npm@5, `prepublish` scripts are deprecated.
npm WARN prepublish-on-install Use `prepare` for build steps and `prepublishOnly` for upload-only.
npm WARN prepublish-on-install See the deprecation note in `npm help scripts` for more information.

> [email protected] prepublish F:\Git\npm-expansions
> npm test


> [email protected] pretest F:\Git\npm-expansions
> node build.js


> [email protected] test F:\Git\npm-expansions
> tap test

total ................................................... 0/0

ok
audited 24 packages in 1.061s
found 3 vulnerabilities (2 low, 1 high)
  run `npm audit fix` to fix them, or `npm audit` for details

Expected Behavior

No vulnerabilities reported

Who

• n/a

References

• n/a

Hello there.

Can i use other languages, like portuguese, for example?

It would be nice if the data included the contributor and a mouse-over on the web site showed their npm account. Just a little easter egg for people to find.

And insufficient of Vespen Gas

the no pants mom one in the middle has no comma after it

Nothing Perfect Matters

Humans aren't very good at editing JSON. The expansion list would be easier to edit as a newline-delimited text file.

PR => #2066

Just a random "И0ДЕ РАСКАGЕ МАНАGЕЯ" proposal. Yay/nay?