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

When I run the devtools, I get the update-notifier message:

   ╭────────────────────────────────────────╮
   │                                        │
   │    Update available 4.4.0 → 4.9.0      │
   │   Run npm i react-devtools to update   │
   │                                        │
   ╰────────────────────────────────────────╯

I appreciate the goal of this message. Ho

In the German translation of electron/docs/tutorial/quick-start.md, the command node -v was incorrectly translated as knode -v.

Is your feature request related to a problem? Please describe.

const readline = require('readline');

const input = readline.createInterface({
	input: process.stdin
});

The code above just hangs.

Describe the solution you'd like

const readline = require('readline');

const input = readline.createInterface({
	input: process.stdin
});

+input.unref(

📚 Docs or angular.io bug report

Description

We have an error message where we're missing the word "flag" or "option".

- This import is never used as a value and must use 'import type' because the 'importsNotUsedAsValues' is set to 'error'.
+ This import is never used as a value and must use 'import type' because the 'importsNotUsedAsValues' flag is set to 'error'.

• I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡

Right now (at least if you use multiple) Autocomplete/useAutocomplete the value that comes back in onChange is always the raw option data. i.e. If you use options=[{value: 'a', label: 'A'}, {value: 'b', label: 'B'}] and select the

Is your feature request related to a problem? Please describe
In my component's props TS interface, I can use JSDoc comments to set the description, and can even use the @default tag to describe the default value 💯
However, nothing happens when I use the @deprecated tag.

Describe the solution you'd like
Some ideas:

• It would be nice i