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

Interaction names longer than about 30 characters are truncated without tooltips and so cannot be seen. If you go to the "Interactions" tab of the profiler, both the left-hand column and the right-hand sidebar are of fixed size and show a truncated name.

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.

Consider the following snippet run in the main process where one wants to listen for "will-prevent-default" events and after some asynchronous operation (do_something, a call which returns a Promise) initiated by the event listener, depending on the result (result) of the operation, call preventDefault on the even

Section/Content To Improve
Config defaults

Suggested Improvement
The documentation teases with a concept of common when setting default header values:

axios.defaults.headers.common['Authorization'] = AUTH_TOKEN;
axios.defaults.headers.post['Content-Type'] = 'application/x-www-form-urlencoded';

Presumably, that mean

test-source-map fails on Windows 10. Looking at the test file, there is a special case for Windows that is not being met under certain conditions. I believe it has to do with how git is configured to handle line endings on checkout but I still need to confirm

C:\Users\jasne\Projects\node>Release\node test\parallel\test-source-map
assert.js:93
  throw new AssertionError(obj);
  ^

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

Similar to #34382.

The completed code download for Universal guide points to 8.x verison of the project in next.angular.io - https://next.angular.io/generated/zips/universal/universal.zip

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

• I have searched the issues of this repository and b

Bug report

What is the current behavior?

Before 4.31.0, webpack never referenced document when it is not defined. After this release, there is code somewhere which assumes a global document is available. This makes it so server side rendering does not work in our application.

If the current behavior is a bug, please provide the steps to reproduce.

Using webpack > 4.31.0

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

I have a chart with values in billions, how do i make the chart look normal without having to scroll 10 pages? 😤

When building and running storybook I would like to be able to pass parameters for angular.json. For instance injecting configurations in Angular is done with "ng serve -c my-config" or "ng build -c my-config" and I would like to do the same when running Angular inside storybook.

As Angular does not support environment variables that is not an option.

Element UI version

2.13.0

OS/Browsers version

mac os

Vue version

2.6.11

Reproduction Link

codepen

Steps to reproduce

1. 百度搜索 element-ui

2. 出现 "该站点可能受到黑客攻击，部分页面已被非法篡改！"

3. Baidu search element UI

4. Appear "the site may be hacked, some pages have been illegally tampered with! "

What

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拉黑了，始终打不开视频。想问问是否有其他视频源可以观看