Describe your problem and how to reproduce it:
This passes:

let favRegex = /favou?rite/i;

But this doesn't:

let favRegex = /favou?rite/gi;

with the error message:

// running tests
Your regex shoul

What problem does this feature solve?

It would allow us to use numbers which is larger than MAX_SAFE_INTEGER.

What does the proposed API look like?

In HTML, {{BigInt("100")}}, {{100n}}, {{2n * 50n}} or {{50n + 50n}} should show "100" (it can be just simply string by using .toString()) at frontend.
At the moment using BigInt in "Mustache" syntax just throw error.
Sure, backu

React extension version: 4.4.0

Steps To Reproduce

1. Install Firefox 72.0.2x64
2. Go to Discordapp.com

The current behavior

Extension reports: "This page does not appears to be using React"

The expected behavior

React is detected (just like it is currently in Chrome/Chromium)

In twbs/bootstrap#30414 we discovered the skip links do not look that well if backported to v4:

We could also improve the theming in v5, in some viewports, it also covers a critical part of the navbar
![image](https://user-images.githubusercontent.com/115592

Update various parts of the text.

There's no such thing as "early ReferenceError" anymore (for things like 0++); they're all just "early SyntaxError" now. tc39/ecma262#691

1. The users of this style guide will probably expect that all of the rules that it prescribes will be enforced by eslint. However, this is not the case - there is a secret, non-documented segmentation where some rules are enforced and others are not, because they would be "too noisy on a legacy codebase". An example of a problematic rule like this is covered in issue #2020. I propose that all of

Is there a way to hide the icon of a BrowserWindow on Windows?

Expected:

Actual:
<img width="68" alt="Screen Shot 2020-02-08 at 11 27 35 AM" src="https://user-images.githubusercontent.com/438516/74090907-194fc800-4a

Section/Content To Improve
Section "Config order of precedence".

Suggested Improvement
The current implementation of

https://github.com/trekhleb/javascript-algorithms/blob/master/src/algorithms/sets/cartesian-product/cartesianProduct.js#L8

I think it makes more sense to return an empty array

// invalid input return null or throw an error
if (!setA || !setB) {
    return null;
}
if (!setA.length || !setB.length) {
    return []; 
}
// or do nothing since the for loop will not trigger anyway

• Version: v10.x
• Platform: all
• Subsystem: repl

What steps will reproduce the bug?

$ node
> function foo() {
... let n = 10n;
Thrown:
let n = 10n;
           ^

SyntaxError: Unexpected end of input
>

How often does it reproduce? Is there a required condition?

Reproduces all the time.

What is the expected behavior?

Should not cause an

We should discuss how to best support a library author providing translations for their library.

Description of the problem

It seems lack of some properties in MeshPhysicalMaterial document.

https://threejs.org/docs/#api/en/materials/MeshPhysicalMaterial

Ever what I noticed are

• clearcoatNormalScale
• clearcoatNormalMap
• sheen
• transparency

We should update.

Three.js version

• Dev
• r113
• ...

Browser

• All of them
• [ ]

To have Deno namespace in the worker, we'll want to provide a map of permissions worker should have. Worker's set of permissions mustn't escalate permissions of parent worker/Deno process.

To achieve that a method called fork should be added to DenoPermissions struct. fork would take as many parameters as there are fields on DenoPermissions and return new DenoPermissions instance a

https://material-ui.com/components/menus/#simple-menu states:

Simple menus open over the anchor element by default (this option can be changed via props).

How can this be changed via props? The page doesn't say. I went to the Menu API page, and I don't see anything simple like open: 'below', or an offset.

Developers have been struggling to figu

Bug report

Documentation Is:

• Missing or needed
• Confusing
• Not Sure?

Please Explain in Detail...

I needed to produce a number of charts with a consistent yAxes logarithmic scale so that users can compare between charts.

I tried setting the same yAxes config settings for each chart:

beginAtZero: true
ticks

Express uses hardcoded values for debug namespace, for example:
https://github.com/expressjs/express/blob/b69b7605b07b41273acc931d25ab585377bcd107/lib/router/index.js#L20

and it is extremly hard to determine in output where things are happening while doing TDD on microservices architecture. It would be nice to allow to specify prefix for namespace, i.e. per microservice which is an express app.

I tried to follow the initial steps from here: https://www.learnstorybook.com/intro-to-storybook/react/en/get-started/

running:

npx create-react-app taskbox
cd taskbox

Then when I ran:
npx -p @storybook/cli sb init

I get the error TypeError: Cannot set property 'storybook' of undefined

This is the full message in my terminal:

 sb init - the simplest way to add a

Existing Component

Yes

Component Name

el-scrollbar

Description

I'm trying to add a scrollbar to an aside menu with el-scrollbar componant but I have some difficulty due to missing entry in the documentation.
My case is exactly the same as the documentation: a fixed header, a scrollable sidebar menu and a scro

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