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

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.
• I

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

merger happened long back, and predates the earliest supported versions.

Describe the solution you'd like
remove references to io.js from the docs, aiming to reduce confusion.

Describe alternatives you've considered
status-quo.

This bit of a hack but it's what we can do at the moment without changing up the internal errors.

To get more accurate error mappings we can try to parse the errno from error message string which may contain the errno from Rust when it is an std::io::Error before falling back to the current approach of switching on error.name.

This is a good first issue.

🚀 feature request

Relevant Package

TS Template added by @mjbvz

TypeScript Version: 4.1.0-dev.20200916

Search Terms

• convert to template string
• refactoring / code action

(see comment for condensed repro of the problem)

Issue Type: Bug

Please consider the following JavaScript example:

const foo = location.h

• The issue is present in the latest release.
• I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

When using the Autocomplete in combination with the TextField, there is a small 'deadzone' where clicking will not trigger the list of options to appear. This deadzone is located b

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

I have been having conflict issues with incompatible versions of google plugins, and have pulled together as much information as I can find, I have removed the gradle plugin from pre Cordova 9

cordova-android-support-gradle-release@3.0.1 - removed now included in Cordova 9.+

and have added to mobile-config.js

App.setPreference('AndroidXEnabled', 'true', 'android');
App.setPreference('Gra