npm

I'm on a 14" macbook M1 pro and get the following error when trying to run a freshly downloaded/installed meteor 2.5.3:

Error: Only 64-bit Intel and M1 processors are supported on OS X

From the blogpost announcing meteor 2.5.1 I would expect meteor to work on my machine.
Given that I'm on an M1, the er

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

pnpm version: >=6.11.0-0

Code to reproduce the issue:

Platform

• version: verdaccio/verdaccio:nightly-master
• platform: docker

Describe the bug
Most of the settings changed in the config.yaml file are not applied.

To Reproduce

web:
  title: "Custom Title" => works
  darkMode: false => works
  showInfo: false => don't works
  showSettings: false => don't works
  showThemeSwitch: false => don't works

Current Behavior

UMD build doesn't support code-splitting and dynamic imports (rollup/rollup#3490, rollup/rollup#3491) due to Rollup current limitations, and tsdx cli don't accept the format option amd when creating build config

Suggested Solution

Consider support AMD module format, o

Describe the proposed change(s).

It seems to be available starting from Node v17. See also:
https://developer.mozilla.org/en-US/docs/Web/API/structuredClone

Hooks for scopes get a double prefix, ie @@scope, when shown with the npm hook ls command. This is due to the response from the web request already including the prefix in the name field, and the following lines of code then locally adding the prefix again, duplicating it.

What rule do you want to change?
vue/no-restricted-class

**Does this change cause th

All preset readme files needs updates for v2