Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug] README.md is not published to npm

See original GitHub issue

When I try lerna publish - npm registry doesn’t display readme, however when I use npm publish - it does.

Issue Analytics

State:
Created 8 years ago
Comments:25 (19 by maintainers)

Top GitHub Comments

9reactions

ianwremmelcommented, Jan 20, 2017

Awesome! Thanks @bcoe! The emoji don’t exist to express my excitement!

6reactions

bcoecommented, Jan 20, 2017

Thanks! Giving credit where credit is due, the whole backend team at npm has been working on infrastructure this makes solving problems like this much easier (we’ve been rolling out a database that was @chrisdickinson’s mad-science idea). I’m really excited to make the tag workflow elegant, for the community and for the benefit of my own OSS projects.

Top Results From Across the Web

NPM readme file showing up broken - node.js

To fix this, remove the readme from the repository, re-add the readme through Github's website, then pull the GitHub repository and republish a ......

package.json

This document is all you need to know about what's required in your package.json file. It must be actual JSON, not just a...

About package README files

Updating an existing package README file The README file will only be updated on the package page when you publish a new version...

npm-publish

Publish a package. ... For example, package.json , README.md , LICENSE , and so on. ... If do not want your scoped package...

gh-pages

Publish to a gh-pages branch on GitHub (or any other branch on any other remote). Latest version: 4.0.0, last published: 8 months ago....