At the moment there is just a list of the package-names:

It would be cool if there were more infos like:

• Latest version
• Publish date
• Maintainers
• …

Clicking on "Website Issues" redirects me https://github.com/npm/newww/issues instead of https://github.com/npm/www/issues .

It would be nice if npmjs.com supported other markup formats than markdown.

Our project uses AsciiDoc and the npmjs.com entry is ugly: https://www.npmjs.com/package/asciidoctor-reveal.js (as of October 3rd 2016).

We are going to work around it by using the packages.json "readme" field so this is not a high priority thing for us.

I understand why you supported markdown first for npm (most bang for the buck). That said, leaving all the others (including plaintext) behind might hurt you in the end. As an inspiration you can look at GitHub's README parser supports several markups. AsciiDoc, Textile, ReStructured Text, RDoc, Mediawiki, etc. Full list here: https://github.com/github/markup#markups

See npm/npm#14159

Cheers!

Hi all,
You probably noticed that GitHub let's you float images on the README markup documents using align="left|right", but npmjs.com does not. This is counter-intuitive since GitHub doesn't have the sidebar on the right, but npmjs.com does — readme's are even more cramped on this website! Supporting the align= attribute on <img> tags would relieve this problem.
cheers,
Roy

Currently, "only" dependencies and optionalDependencies are included, not peerDependencies.

I have two repositories out there with different capitalizations. Everytime I try to unpublish one of them I am getting a 400. (Registry returned 400 for delete).

The one I want to delete is Leaf.js not leaf.js

https://www.npmjs.com/~leaf.git

Broken: https://www.npmjs.com/package/@types/jquery

Works: https://www.npmjs.com/package/@types/jqrangeslider

Both of these packages have a README.md; the only difference seems to be that anything we recently published isn't displaying its README properly.

For example, on this module page, "Try it out" has the old TonicDev icon, and tonicdev.com URL.

What's the feature?

To provide analytics about what node version & what OS they are using. Both globally and for individual package.

What problem is the feature intended to solve?

It helps to judge whether to use ES6 features without Babel or work just with ES5. also helps you to know if you can drop obsolete code like polyfills
Could also help to know what platform they are running so you can write OS startup script for example

Hi there,
the form to add collaborators to a package seems to be without style.

If I enter the name of an npmjs user and press "enter" it works, but it does not show anything else but the input box.

I'm using Chrome Version 52.0.2743.116 (64-bit)

Thanks!

Instead of just making the repo private, maybe the current content (and git history?) could be placed in a branch on this repository.

People who want to see July 2016's source code for the site would still be able to.

Any thoughts?

I was looking at the Picturefill page on npm and happened to be at a viewport size where the command npm install picturefill was cropped to read:

The issue happens at around 940px viewport width.

NPM appears to use a parser that follows the common mark spec and it differs from github in a few ways. My issue is writing a single backslash in an inline code block.

The Github way is

`\`

But that trips up the NPM parser, since common mark treats that as an escaped backtick. The right way to do it for NPM is

`\\`

But that messes up github, which interprets it as 2 backslashes.

I'd guess that most modules use the github markdown style, so I guess I would consider this a npm website bug

https://www.npmjs.com/package/socket.io-client

I've started prefixing my packages with @myName/packageName as suggested in the blog here: http://blog.npmjs.org/post/116936804365/solving-npms-hard-problem-naming-packages.

The problem is that the download stats aren't working on these packages, as confirmed here: https://twitter.com/seldo/status/744418097113636864

Do we have a status update for this?

Thanks all.

Hello,

We use npm with shrinkwrap in our project, with gulp-html-autoprefixer as a dependency in package.json.

We fixed it at 0.1.0 some time ago, the same as the latest dependency in their github :
https://github.com/Rebelmail/gulp-html-autoprefixer/blob/a0d226053c1e1507c1669ed991a17b990a795b70/package.json

Unfortunately and apparently for some time now, the latest version reported by npm is 0.0.1
https://www.npmjs.com/package/gulp-html-autoprefixer

When we run npm install, it won't find the latest version (0.1.0), forcing us to use the previous one (0.0.1).

Would it be possible to update it to the latest versin? Is there a bug causing it take the previous one?

Thanks!

Reported error:

npm ERR! registry error parsing json

What's really happening:

npm http request PUT https://registry.npmjs.org/-/user/org.couchdb.user:ginden
npm http 503 https://registry.npmjs.org/-/user/org.couchdb.user:ginden
npm verb bad json 
npm verb bad json <?xml version="1.0" encoding="utf-8"?>
npm verb bad json <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
npm verb bad json  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
npm verb bad json <html>
npm verb bad json   <head>
npm verb bad json     <title>503 No healthy backends</title>
npm verb bad json   </head>
npm verb bad json   <body>
npm verb bad json     <h1>Error 503 No healthy backends</h1>
npm verb bad json     <p>No healthy backends</p>
npm verb bad json     <h3>Guru Mediation:</h3>
npm verb bad json     <p>Details: cache-lhr6333-LHR 1477058331 3170619141</p>
npm verb bad json     <hr>
npm verb bad json     <p>Varnish cache server</p>
npm verb bad json   </body>
npm verb bad json </html>

It seems like your servers return HTML on certain errors but npm expects JSON as return.

EDIT: closed as duplicates of https://github.com/npm/registry/issues/69

Allow search ordering based on common criteria such as:

• Number of starts
• Number of downloads
• Recently updated
• ?

The npm website does not integrate with GitLab to provide GitLab metadata information on a per-package basis.

For example, I cannot view the number of stars, and open issues and merge requests, for my semantic-release-gitlab project, which is hosted on GitLab

Currently, www.npmjs.com does not show if a package is deprecated. A red banner just above the readme would be fitting. Some sort of indication in search results would be nice too. A warning is shown in the command line after you have chosen to install a package but not while you are choosing/viewing it online.

Thanks!

npmjs.com is double-encoding ampersands (&) from the description line in package.json.

So, this:

Turns into this:

Which renders as this:

It's not the end of the world, but it's not correct either :/

Are you having issues with your varnish cache on the npm website?

I noticed a module showing the incorrect version.

The latest version of approvals-server at the time of writing is 0.2.0, however the version shown on https://www.npmjs.com/package/approvals-server is 0.1.2.

When installing 0.2.0 is installed so this seems only to be a problem with the website cache.

Would be nice to have the ability to change the npm profile picture without having to create an account on a third party service like Gravatar. Uploading directly to npm could be a possibility or maybe set it to use the profile picture that is used on GitHub?

Hi! The "website issues" link, which I've deduced should link to this very issue tracker, appears to have the extra characters we in it for some reason – like so: https://github.com/npm/newww/issues.

Oops! Ironically, it took me a while to find where to post this issue ;)

There were over 700 issues in the old repo, including various relevant historical information about the growth and decision-making of npm. It's a shame to have all that historical data made inaccessible. I strongly encourage you to export a copy of it (there are many scripts floating around, I can provide specifics if wanted), and make that available somewhere (either on the npm website, or simply upload it to the Internet Archive as an item).

I use some special characters (backticks for example) in published package description. npm site parses it as Markdown text. But they display as escaped HTML in package page like below:

It should not be parsed as Markdown.

Some pages on the npmjs.com don't reflect the latest version of the package.

For example: convict.
According to the page: "types published 4 weeks ago" and "0.6.32 is the latest of 13 releases".
But according to npm info @types/convict, version 0.6.33 was published 3 days ago (Sep 19).

This may be because of our publish script: we are directly using the publish method from npm-registry-client.
Currently we use a very simple technique to get the metadata: we read in the contents of README.md and attach it to the package.json.

Similar to #11, I suspect that we are still not providing all of the metadata needed. Is there something else we need to be doing there?

Here is the list of packages with outdated pages (produced by a script):

• @types/convict
• @types/escodegen
• @types/eventemitter3
• @types/express
• @types/jdataview
• @types/js-cookie
• @types/js-yaml
• @types/parse5
• @types/passport
• @types/pathwatcher
• @types/pg
• @types/tape
• @types/temp
• @types/thrift

Hey everyone, I noticed a while back that scoped modules do not show stats, can we get those added or is that not feasible right now?

Hi when I visit https://www.npmjs.com/ this website doesn't display correctly. The logo is misaligned and the login button too. But this displays properly on chrome. I looked on the f12 tools and it shows it is using webkit specific code like -webkit-* which wont work on internet explorer. Please could this be fix?

I've been trying to publish updates to the README.md for package react-pub-sub. It is part of a lerna repo at the moment and therefore some of the links to its git repo do not actually exist yet (my understanding is that README is not pulled from git so shouldn't be a problem). I have published a few patch / minor versions now and the README has not reflected.

git --version: 2.8.1.windows.1

npm --version: 3.10.6 (linked)

package.json

{
  "name": "react-pub-sub",
  "version": "0.7.0",
  "description": "Factory for creating prop and state propagation between 1:N React components.",
  "main": "lib/index.js",
  "files": [
    "lib"
  ],
  "keywords": [
    "react",
    "pubsub",
    "publish",
    "subscribe",
    "propagate",
    "propagation"
  ],
  "scripts": {
    "start": "run-p build-watch",
    "clean": "run-p clean-lib clean-doc",
    "clean-lib": "rimraf lib",
    "clean-doc": "rimraf doc",
    "prebuild": "npm run clean",
    "build": "babel src/lib -d lib",
    "build-watch": "npm run build -- --watch",
    "release": "npm version patch && npm publish",
    "postrelease": "npm run release-gh-pages",
    "prerelease-gh-pages": "npm run doc",
    "release-gh-pages": "run-s gh-pages-subtree gh-pages-push gh-pages-delete",
    "postrelease-gh-pages": "npm run clean-doc && npm run git-save -- clean && git push -u origin master --follow-tags",
    "predoc": "rimraf doc",
    "doc": "esdoc -c ./esdoc.json && ncp CNAME doc/CNAME",
    "postdoc": "npm run git-save -- doc",
    "gh-pages-subtree": "git subtree split --prefix doc -b gh-pages",
    "gh-pages-push": "git push -f origin gh-pages:gh-pages",
    "gh-pages-delete": "git branch -D gh-pages",
    "git-save": "git add -A && git commit -am ",
    "upgrade": "ncu -a && npm update"
  },
  "dependencies": {
    "babel-runtime": "^6.9.0",
    "chai": "^3.5.0",
    "eventemitter3": "latest",
    "ncp": "^2.0.0",
    "react-stamp": "latest",
    "solvent": "^0.7.0"
  },
  "devDependencies": {
    "babel-cli": "^6.9.0",
    "babel-core": "^6.9.0",
    "babel-eslint": "^6.0.4",
    "babel-loader": "^6.2.4",
    "babel-plugin-react-transform": "^2.0.2",
    "babel-plugin-transform-runtime": "^6.9.0",
    "babel-polyfill": "*",
    "babel-preset-es2015": "^6.9.0",
    "babel-preset-react": "^6.5.0",
    "babel-preset-stage-0": "^6.5.0",
    "babel-register": "^6.9.0",
    "esdoc": "^0.4.7",
    "esdoc-es7-plugin": "0.0.3",
    "eslint": "^2.12.0",
    "eslint-plugin-babel": "*",
    "eslint-plugin-react": "*",
    "faker": "^3.1.0",
    "mocha": "^2.5.3",
    "npm-run-all": "^2.1.1",
    "react": "^15.1.0",
    "react-addons-test-utils": "^15.1.0",
    "react-dom": "^15.1.0",
    "react-tools": "^0.13.3",
    "rimraf": "^2.5.2"
  },
  "author": "Cole Chamberlain <[email protected]> (https://github.com/cchamberlain)",
  "bugs": {
    "url": "https://github.com/noderaider/react-pub-sub/issues"
  },
  "homepage": "https://react-pub-sub.js.org",
  "license": "MIT",
  "repository": {
    "type": "git",
    "url": "git+https://github.com/noderaider/react-pub-sub.git"
  }
}

.npmignore

# Logs
logs
*.log

# Runtime data
pids
*.pid
*.seed

# Directory for instrumented libs generated by jscoverage/JSCover
lib-cov

# Coverage directory used by tools like istanbul
coverage

# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
.grunt

# Dependency directory
# Commenting this out is preferred by some people, see
# https://npmjs.org/doc/faq.html#Should-I-check-my-node_modules-folder-into-git
node_modules
docs/html

# Users Environment Variables
.lock-wscript

.DS_Store

At https://www.npmjs.com/support,

website issues on GitHub

points to a wrong repo.

Seeing the following issue on npmjs.com

Replica of https://webcache.googleusercontent.com/search?q=cache:aA5eZUjNlt0J:https://github.com/npm/npm-www/issues/569+&cd=1&hl=en&ct=clnk&gl=ca (posted by @davidbourguignon)

Hi all,

On the signup page (https://npmjs.org/signup), there is a clear warning: the email address provided will be public.

However, after checking some account pages source code, these addresses do not seem to be even "cloaked" or somehow protected from robot harvesting (http://www.robelle.com/tips/email-cloak.html).

Why? Am I naively missing the point here? Thanks in advance for your help!

Best regards,

David.

It doesn't look like it's been resolved yet.

currently we do this :

we should do what github does:

trying to see what packages are available, but there are only a few of our packages in the ui :/

rather than truncating the list, it'd be super nice if it was paginated instead

Hey npm folk 👋. Thanks for all the hard work you do 👍.

It would be really handy to be able to add notes/names to access tokens on the tokens page. Some tokens are kept around for things like Travis CI - it'd be nice to add a little note/name to those so when we go back to the page we can see which is for what (kind of like github does with personal access tokens) 😄.

I modified my name, but it didn't update in my profile page.

For example see kotlin package

My package has 2 readme files - one for npm called npm.md, and another for my GitHub repository, called README.md. When I package my app and publish it, I have a script that renames these readme files, so npm.md becomes README.md and the original README.md becomes ORIGINAL.md. npm should display the README.md in my package, as opposed to displaying the README.md from my GitHub repo, since they're different in this case. This was working correctly until about 6 months ago. My packages where I see this issue are:

• forcedroid
• forceios

many cultures do not have this name construction, and also this name construction does not afford us any value. it should be a single field with little validation.

a good read: https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/

There is no favicon in Firefox browser, I checked on two different machines, on Windows 10 and in Ubuntu 16.04, in Chrome it is available on both machines.

Hi all !

When you explain how to use "md-grid-list", I found a little error on the typo of grid-list.

import {MdGridListModule} from '@angular2-material/gridlist/gridlist'; FALSE
import {MdGridListModule} from '@angular2-material/grid-list/grid-list'; TRUE

@NgModule({
  imports: [MdGridListModule],
  ...
})
export class MyAppModule {}

https://www.npmjs.com/package/@angular2-material/grid-list

Have a good day !

It would be nice to see a dependents count on individual module pages, much like the dependencies count that already exists.

See this link inside a <h2>.

I'd say a correct rendering should not include the :before hash and it should likely be colored. 😉

We keep getting below message when adding a new user:

504 Gateway Time-out
The server didn't respond in time.

The user is actually added, but we shouldn't be getting this error. It may be because your Fastly backend definition may need its timeout setting adjusted, to allow your origin backend to finish its response.

on the packages view, i see 1577 "teams":

on the "team" view, i only see 100:

Package maintainers currently have to guess on which node.js versions (engine versions) their packages are installed. So their decision to keep supporting e.g. node v0.10 or move up to a newer version is also based on guesswork. Likely, many packages are moving towards node >= 4 in order to make use of the new ES6 features and at the same time enterprise apps in particular loose support. As you can see in this article old node.js versions are still heavily used.

It would be great if npm would track the node.js versions a package gets installed into. Then showing these statistics on the npm website along with the download counts would be really helpful.

IMHO this would be a feature that will contribute to the healthy package ecosystem.

Go to https://www.npmjs.com/package/@angular/router

Click the "and more" link in the Dependents list:

this goes to

https://www.npmjs.com/browse/depended/@angular/router

which is looking for a missing wombat 😢