The GIF over here depicts fCC in its old design. Even though I don't think there's anything wrong with it, I guess it should be updated to align with how fCC looks now

![image](https://user-images.githubusercontent.com/34807532/70627002-6e7c8280-1c4b-11ea-87d

Version

2.6.10

Reproduction link

https://github.com/vuejs/vue

Steps to reproduce

1. compare the AsyncComponentFactory definition with the document

What is expected?

attribute 'componen

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
When Chrome Devtools are in "dark mode", all the standard panels have a dark scrollbar:

However, the React Devtools still show a light scrollbar:

What is the expected behavior?
Scrollbars

As we’re using the same navbar across all our projects now—docs, icons, and blog—I’m wondering if we should be linking to our GitHub org profile instead of the Bootstrap (or Icons) projects in the main navbar.

Thoughts @XhmikosR, @MartijnCuppens, @ysds, @Johann-S?

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.

The typings file specifies:

setVibrancy(type: 'appearance-based' | 'light' | 'dark' | 'titlebar' | 'selection' | 'menu' | 'popover' | 'sidebar' | 'medium-light' | 'ultra-dark'): void;

whereas docs suggest that passing null disables vibrancy.

The argument type should be nullable

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

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.

https://github.com/trekhleb/javascript-algorithms/blob/dc1047df725117c411959692a1ab538f65342b2e/src/algorithms/math/fibonacci/fibonacci.js#L13

This condition is redundant, the while condition covers the case where n equals 1.

p.s- I will exploit this opportunity to say thank you for this repository.

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 );

Found with @RyanCavanaugh

interface Dog {
    barkable: true
}

declare function getRover(): Dog;

export let x: Dog = getRover;

Expected

Type '() => Dog' is not assignable to 'Dog'.(2741)
  input.ts(7, 21): Did you mean to call this expression?

Actual

Property 'barkable' is missing in type '() => Dog' but required in type 'Dog'.(2741)
  input

📚 Docs or angular.io bug report

Description

I)n the insertBefore() method, it says that refChild p

Description

So our function arrayToHtmlList is in a pretty bad space and could use an update. We already had some discussion over at #675 but I wanted to move the update discussion over to an issue for more visibility.

Current problem:

It uses an awkward query selector instead of the `document.prototype.getElementBy

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

Link color stays as if the theme was light (default)

Expected Behavior 🤔

Link color becomes brighter as in the examples on MUI docs.

Steps to Reproduce 🕹

https:

Feature request

Support optionalDependencies as NPM and Yarn do:
http://npm.github.io/using-pkgs-docs/package-json/types/optionaldependencies.html
https://yarnpkg.com/lang/en/docs/dependency-types/

It's useful for example when you need to use an package in Windows and other in Mac/Linux and packages support os t

Prerequisites

• Put an

If you follow the readme procedure, the following error will occur in the first npm install express.

saveError ENOENT: no such file or directory, open '/xxx/xxx/package.json'

As you know, the cause is package.json does not exist.
Other users seem to have a similar error, so it seems better to add npm init to the readme.
Or I thought it would be nice to bring a link `Please follow

Documentation Is:

• Missing or needed
• Confusing
• Not Sure?

Current documentation

Having a look to the current documentation, the chain to set the datasets options is:

• per dataset: dataset.*
• per chart: options.datasets[type].*
• or globally: Chart.defaults.global.datasets[type].*

Wha

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

是

Component Name

table

Description

when i call toggleAllSelection function , the select-all were emited。but the document describe select-all will be emited when user click the button。I think the md document should describe the feature correctly

On Meteor 1.8.1 this is maybe true for browser-policy package, but it is not really true for any realistic Meteor app these days because apps use ecmascript which requires dynamic-import, which enabled eval by default. So in practice, by default, eval is enabled. See #10704.

It should be probably clarified in the README that the package by default keeps it disabled, but Meteor apps by

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

Challenge Build a Tribute Page has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.100 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.

好像VIMEO把GOOGLE的云服务器IP拉黑了，始终打不开视频。想问问是否有其他视频源可以观看