Challenge: https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures/basic-data-structures/add-key-value-pairs-to-javascript-objects

The challenge is part of the Basic Data Structures. It seems completely redundant, not to mention incorrectly implemented.

1. It is redundant because we already have [a challenge](https://www.freecodecamp.org/learn/javascript-algorithms-and-d

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

Feature request from a DevTools user at Faceook:

If I mouse over a node in the flame graph if you can highlight it in the view like the inspector that would be really amazing!

The hamburger menu button in v4 and upcoming v5 documentation on small screen lacks a visible focus indication (e.g. when navigating by keyboard)

![v4 header with hamburger menu button](https://user-images.githubusercontent.com/895831/77048035-b08d3100-6

Chapter in question: https://github.com/getify/You-Dont-Know-JS/blob/master/es6%20%26%20beyond/ch2.md#template-literals

The suggestion seems to be that the template literals would be all about strings; there's only examples that result in strings, and phrases like "final string value" and "generating the string from the literal" are used in what should be a general context, but the tag function

The max-classes-per-file rule is enabled in rules/best-practices.js but there is no mention of this requirement in the docs. If this is a best practice, I'd like to know why.

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

Even though --max-old-space-size is a V8 flag, I would expect us to document it, given that it’s probably the most useful V8 flag for Node.js users overall.

Refs: #32251

Huge and nice collection and also getting very much appreciated from the community.
It would be great if somebody can translate into English then it will be reaching out to global.

This is about AvlTree.js - rotateLeftLeft, rotateRightRight method
rotateLeftLeft should be call 'caseLeftLeft' or 'rotateRightRight'.
Because base on the image on avi tree readme.md, rotateLeftLeft method is a right-right rotation.

📚 Docs or angular.io bug report

Description

The API docs (https://angular.io/api/core/DebugElement)

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
• [ ]

In microsoft/TypeScript#36187, @a-tarasyuk wrote up a handy error message for non-exported types. We should provide a quick fix to add the export modifier for declarations like this that aren't in node_modules and the like.

The classes property is missing from the prop type of CssBaseline and ScopedCssBaseline, while the docs mentioned that the prop should exist: ScopedCssBaseline API and CssBaseline API

mapObject's explanation is not up to standards with our current format. It should be updated to match the rest of the snippets.

We could also make the example a one-liner.

Bug report

Prerequisites

• Put an

Looking at this,
https://github.com/expressjs/express/blob/master/lib/request.js#L79

It seems like express checks referrer (with two "r"s) first, then referer next.
Is there a particular reason why the double-r is checked first?

It seems like single-r should be checked first because it's standard.

Another reason to check single-r first is because it's easier to spoof double

Tooltip animation configuration is not documented.

The defaults are in Chart.defaults.tooltips.animation.
The default config is:

	animation: {
		duration: 400,
		easing: 'easeOutQuart',
		numbers: {
			type: 'number',
			properties: ['x', 'y', 'width', 'height'],
		},
		opacity: {
			easing: 'linear',
			duration: 200
		}
	},

_Originally posted by @benmccann in htt

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

It'd be nice to have the following types from __domTypes exposed in the global scope:

• HeadersInit
• RequestMode
• RequestInit

(I'm sure there's more types, but these are the ones that I ran into that weren't exposed like they are in TypeScript.)

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

I think it is worth mentioning that the solution stated Catching unresolved and rejected promises is not always valid. what I mean is that if a promise is caught on a later turn of the Node.js event loop, then probably throwing an error on this global catch is not a good idea. I am wondering how this is counted as best practice while obviously from the node official documentation it should

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

The Head section says:

The next 2 meta tags (Charset and Viewport) need to come first in the head.

I found a reference for Charset being early on in the head:
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta

The <meta> element declaring the encoding must be inside the <head> element and within the first 1024 bytes of the HTML as some browsers only look at those bytes be

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