monorepo

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

mapbox-gl-js version:2.6.1

browser:Chrome

Steps to Trigger Behavior

1.create LngLatBounds as bounds
2 .use map.fitBounds and pass the center option to it

Link to Demonstration

check out this link for more info:
https://jsbin.com/zodotod/edit?html,output

Expected Behavior

The bounds should be in the view and the center of the map should be the `cen

What version of Turborepo are you using?

1.1.7-canary.5

What package manager are you using / does the bug impact?

npm

What operating system are you using?

Mac

Describe the Bug

All the task log lines are prefixed

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

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

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

Pants uses lots of PEXes "internally", which are never exported for users to consume. Since these are implementation details, we have free-reign to choose an internal-default PEX compression level... and some values can make a considerable difference in performance.

To experiment/adjust for "internal only", logic similar to the logic for PEX's `lay

Depends on #1048

Another Ethers issue 😄 : I lately had the use case where I wanted to pull in some tx data via RPC with Ethers which I wanted to use in some client testing context but I finally gave up since the conversion to our tx format here was not so clearly spottable and I used some direct client data extraction

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