Given the immense popularity of Docker and the need to harden it different per platform (see ideas below) - we'd like to start writing a Docker best practices section.

You're welcome to contribute ideas and write best practices - writing and brainstorming will people is an amazing way to deepen your Docker understanding.

At first, we want to collect ideas for best practices, solidify a list

Some of the issues below are already mentioned in other tickets, but I have the feeling that a proper generic issue is due to give it visibility, as for now the current package is unusable for many users.

1. The typescript package doesn't respect the tsconfig flags, and many of them are hardcoded inside the meteor/babel package.
   I understand that meteor needs to control some compilation option

Do you want to request a feature or report a bug?
feature request

What is the current behavior?
Currently yarn why won't indicate any package info in the resolutions field

If the current behavior is a bug, please provide the steps to reproduce.

1. install a package with any version, e.g "pkg": "^1.0.0"
2. add resolutions field in package.json, pkg: "1.0.0"
3. upd

Expected Behavior

It should be possible to customize the header of the generated changelog (or omit it completely).

Current Behavior

The changelog header is hardcoded in https://github.com/lerna/lerna/blob/master/core/conventional-commits/lib/constants.js

Possible Solution

A `command.publish.changelogHea

We need to add tests for source/util.js, source/version.js, source/git-util.js and source/npm/util.js.

There is a $60.00 open bounty on this issue. Add mo

I use git-bash (like probably nearly all windows npm user).
if i run mkdir -p plop it create me plop folder if not existant and do nothing if it exist.
if i do the same as npm task or with npm-run-all it create me -p folder and plop if they don't exist and fail if there already there.

is'nt possible to use git-bash command in priority when available ?

What / Why

The footer of at least some pages on the docs website (such as https://docs.npmjs.com/cli-commands/update.html) contains

To report bugs or submit feature requests for the docs, please post here. Submit npm issues here.

where "post here" goes to https://npm.community/c/support/docs-needed. However, that page does not seem to have any ability to post new pages, and the last

Tell us about your environment

• ESLint version: 5.9.0
• eslint-plugin-vue version: 6.1.2
• Node version: 10.13.0

Please show your full configuration:

It's great the github releases are automatically generated, but as a user of changelogs I find it more useful to just look at a single Changelog.md file instead of having to page through (sometimes) numerous pages of github releases to understand all the changes that happened between the version I was at and the latest.

It would be great if release were to also automatically generate and upda

Saw a great recommendation from @iarna on the package.community Discord channel which I just joined.

Decentralized contribution info or no, I'd like npx thanks to point folks where to learn about how to add themselves. So it's less of a "cool kids" thing

Totally agree. I was planning to add this but forgot to do it.

Also, it's not "@apify/httpRequest" package but "@apify/http-request"

If behind a proxy, the installation in Powershell will not work. The readme should mention that this is fixed by setting up proxy in Powershell:

$env:HTTPS_PROXY='http://proxy:port'
$env:HTTP_PROXY='http://proxy:port'

Open call to anybuddy who wants to refine the logo! 🎨

The current graphic is not looking that brilliant:

A smoother refine would be awesome!
Unfortunately there is no .svg available, the original file it's a .psd ->>
📂

• https://github.com/720kb/media/tree/gh-pages/ndm

Any h

I'd appreciate if there was a comparison of lite-server with http-server which is the most popular www dev server for node.js (according to npm, 3 times more downloads than lite).

So .npsrc was provided by this PR, sezna/nps#198.

However, there is no documentation.

From https://github.com/npm/validate-npm-package-name:

package name should not start with . or _

Try to replace tarballs to _tarballs from URL to avoiding conflict.

The 00th challenge tells you what to do but not how to.

• "The first thing we're going to do is make sure that your npm version is up to date."
• "Run how-to-npm verify once that is done."

But actually, the way to do this challenge is to give that command, right? That's what worked for me. I can create a PR if this is actually what's wrong. Not sure how to do the i18n though..