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

I have a project that is in a monorepo and uses yarn right now.

I'm considering migrating to pnpm for the monorepo, as well as all other projects I contribute to, as I have a small SSD as local storage (and with Windows...). However, it would be ideal if there was compatibility between yarn's workspaces and pnpm, so that we don't have to jump "all in" to it.

To this end, yarn allows packages

Current Behavior

For every new project I start with TSDX, one of my first steps is to add stubs for static assets and stylesheets - as detailed on the Jest docs.

Desired Behavior

Add Jest file stubs in to the TSDX setup.

Suggested Solution

Following the Jest docs

// package.json
{
  "jest": {
    "m

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 ?

Description

npkill lists the home directory as a node_modules directory:

Reproduction

1. Run npkill --sort size.
2. Wait for search to complete.
3. Do other tasks, and return to the process.
4. /Users/user/. will appear on the list.

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

package.json's main field seems to be aimed directly at npm, not browsers. So perhaps if there are no jsdelivr or browser fields, then the /dist folder should be the next highest priority when looking for the default file?

Example:
spectacle: main (so jsdelivr's default) = [/lib/index.js](https://cdn.jsdelivr.net/npm/spectacle@4.3.

What Renovate type are you using?

I am using Renovate in a private project hosted on Gitlab.com

Describe the bug

It's not a bug but a simple typo. If you start using Renovate, it will usually create a "Pin dependencies" pull request. The PR template contains a

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:

readme says:

[Windows Vista / 7 only] requires .NET Framework 4.5.1 (Currently not installed automatically by this package)

but actually it requires .NET Framework 4.6 :

windows 7 64bit sp1

💡 Feature description

JSDoc comment is a well-known tool to add a document in code/d.ts file.

JavaScript/Typescript language server recognizes jsdoc comment so that famous editor's IntelliSense recognizes jsdoc.

However, As far as I know, there is no way to add JSDoc comment. So, currently, I need to create a wrapper npm package to control d.ts.

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'

Some folks have noted it would be beneficial to have this repository translated to other languages. One contributor has already volunteered to translate the repository into Russian (woohoo!).

If anyone has the time and drive to help out with other languages, please reply below with the proposed language and I'll give you the "go-ahead"... just to make sure two people don't create translations i