Following up on the comment on PR 38309, the following English challenge tests need to be updated as described, as the non-English version were translating these when they should not have been translated.

• Standardize Times with the HTML5 datetime Attribute
  Issues: All tests need to be re-translated

• Use

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)

Per twbs/bootstrap#29956.

In What about &&? section we have the following code.

function foo() {
    console.log( a );
}

var a = 42;

a && foo(); // 42

result in comment should indicate that foo was called. but in fact we would get same result of "42" if first operand had been called (like in || operator). i think results of a and foo() should be different to make the example be clearer.

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 in main readme around performing multiple concurrent requests

Suggested Improvement
There is a request to remove axios.all and axios.spread (axios/axios#1042)

Although the functionality has not yet been removed, we can at least stop advertising it if there is intent (with good reason) to remove it. We can still keep

When not using a file extension in ESM - eg import pkg from './path' we currently just throw a straightforward not found error. As proposed by @MylesBorins in nodejs/modules#443 it would be useful to enhance this error message.

Ideally the error message should run the CJS resolver and say "the CJS resolver would have resolved this module to ...". We actually previous

The deprecated decodeDracoFile method should be removed and replaced with a parse method similar to other loaders. Currently decodeDracoFile does not propagate errors, and should do so. So probably a signature like:

dracoLoader.parse( arrayBuffer, /* options, maybe? */, onLoad, onError );

🐞 Bug report

Command (mark with an x)

• new
• build
• serve
• test
• e2e
• generate
• add
• update
• lint
• xi18n
• run
• config
• help
• version
• doc

Is this a regression?

Yes, this command did not generate errors using Angular 8

Description

We have renamed the production build configu

• 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 😯

The Autocomplete component uses a very light default option highlight and doesn't exposes any CSS props to easily change it as far as i can tell.

Expected Behavior 🤔

an easy

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

Is express using semver for versioning? It's not readily obvious. Node.js has picked up the practice of labeling issues as semver-major or semver-minor to help differentiate breaking vs additive changes. I'd recommend something similar here to help keep things organized.

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

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'https://storybookjs.now.sh/official-storybook/?path=/story/addons-jest--with-tests'
   in a narrow width browser.
2. Click on the Tests panel.
3. Scroll down to see the tests panel.
4. See the total number of tests and total time covering up the "Todo" tex

Element UI version

2.13.0

OS/Browsers version

mac os

Vue version

2.6.0

Reproduction Link

https://github.com/ElemeFE/element/blob/dev/packages/

Steps to reproduce

https://github.com/ElemeFE/element/blob/dev/packages/tabs/src/tabs.vue
line 61 vnode.componentOptions && vnode.componentOptions

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

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

Feature Request

Ionic version:
[x] 4.x or 5.x

Describe the Feature Request
Currently if you present multiple toasts in the same position they show on top of one another which looks like a bug.

Describe Preferred Solution
I would suggest one of two things:

1. Implement toast stacking. If you present multiple toasts, they display in a list like the phone's notifi

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

Tabs in cards are not working in new v.1.0.0.

I have tested on starter template.

Let me know if you need further information.

Thanks for your help.