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

This issue / feature request was originally posted by @AndrejGajdos

mapbox-gl-js version: 1.10.1

Question

Mapbox GL provides option scrollZoom to enable/disable zooming on scroll and pinch-to-zoom events. Is it possible to allow zooming on pinch-to-zoom and disable scrolling on scroll event?

Links to related documentation

https://docs.mapbox.com/mapbox-gl-js/

In Settings : 'Add a new side account' button

Step #2 in Side account creation

(a very light & quick version of onboarding, with only nickname step)
![side account mode copy](https://user-images.githubusercontent.com/37345040/99953009-dd7db900-2d80-11eb-9f6f-e

MGLTilePyramidOfflineRegion should have a countOfTiles method that returns the number of tiles included in the tile pyramid. The implementation would rely on the mbgl::util::tileCount() function added in #9906.

This is the iOS/macOS equivalent to #11108 for Android. It would serve as a built-in alternative to mapbox/turf-swift#47 for applications already using the map SDK, including applica

Let's add MinVer and on successful builds generate a release.

Real User-Agent is detectable with <iframe> when using "puppeteer-extra-plugin-stealth". To prevent it use "'--disable-features=site-per-process'" argument for puppeteer.launch(). See explanation: puppeteer/puppeteer#2548

Real screen size is also detectable with iframe, to prevent it I used preload() script.

OS: Windows 10
"puppeteer": 3.0.4
"puppeteer-extra": 3.1

Right now it fails in all sorts of subtle ways relating to failures to resolve requirements and picking weird interpreters (e.g., due to the issue explained in pantsbuild/pex#957).

It hypothetically possible to build lambdas on MacOS if all transitive requirements have prebuilt linux wheels, but that is too narrow a case to support, and it's subtle and tricky to get ri

The published package in NPM only contains the /dist/* files but when debugging with i.e. the Chrome DevTools and stepping into the library, an error is thrown because the original /src/*.ts files cannot be found and therefore the sourcemaps can't be used to display the proper source lines being executed.

Please update the NPM package to also include the /src directory.

Other packages

There is an issue when adding new languages that I believe is related to react suspense. See i18next/react-i18next#977

Error:

Steps to reproduce:

1. Add a new language to Locize.
2. Make su

I tried to create an iOS release build.

Steps to reproduce:

1. install pods
2. open Xcode Workspace
3. edit schema to release
4. start build

Looks like the bundler doesn't know the "ios" platform => no bundle creation.
"error Invalid platform "ios" selected"

+ node /Users/userName/RN-mono/node_modules/react-native/cli.js bundle --entry-file index.js --platform ios --dev fals

In packages/components-typescript/package.json the fields main and main:src: refer to files that do not exist:

  "main": "src/index.tsx",
  "main:src": "src/index.tsx",

The index.tsx file is located in packages/components-typescript/index.tsx

Are these two fields redundant?

package.json supports shortcut syntax for the repository field (https://docs.npmjs.com/files/package.json#repository)

orgname/reponame is very common

I left a review and then got this message

which seems strange as it's telling me something I know.