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

What problem does this feature solve?

I just spent way too long debugging something really weird until I realized I accidentally wrote :v-if instead of v-if.

A warning when wrongly using shorthands like : on "native" vue attributes could prevent this bad experience easily.

What does the proposed API look like?

:v-if="foo"

--> console.warn("You specified v-bind:/ v-on:

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

I had a nice issue description before github/related issues-beta ate it, here's the gist:

https://getbootstrap.com/docs/4.3/utilities/flex/#justify-content

The flex justify documentation examples only display equal-width items (<div>Flex Item</div>).
It might be wise to add one or two examples with non-equal-width divs and more than 3 cols.

Specifically to illustrate that the middl

Update various parts of the text.

There's no such thing as "early ReferenceError" anymore (for things like 0++); they're all just "early SyntaxError" now. tc39/ecma262#691

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

Currently when using the --experimental-resolve-self flag, with the following:

{
  "name": "test",
  "exports": "./test.js"
}

If including a require('test') in the test.js file and running node --experimental-resolve-self pkg/test.js this will throw an error.

It works with "main" and exports subpaths though so may be a sugar-specific or main-specific error case fo

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.

const leftNode = new BinaryTreeNode(1);
const rightNode = new BinaryTreeNode(3);
const rootNode = new BinaryTreeNode(2);
rootNode
  .setLeft(leftNode)
  .setRight(rightNode);
expect(rootNode.traverseInOrder()).toEqual([1, 2, 3]);

const replacementNode = new BinaryTreeNode(5);
rightNode.setRight(replacementNode);
expect(rootNode.traverseInOrder()).

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

Currently, there's detailed info in

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

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

I want to use Chart.js in IE9 but now it only supports IE 11+.

I remembered that the old versions (i.e. 2.5.0) supports IE 9+, but the links always pointed to the latest documentation. So where can I find documentation for historical versions?

I searched the issues but did not get an answer. Thanks.

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.12.0

OS/Browsers version

Windows 10 Chrome

Vue version

2.6.10

Reproduction Link

https://codepen.io/ndionne/pen/rNNZweY?&editable=true

Steps to reproduce

Column with type selection in empty datalist

What is Expected?

Checkbox should'nt be checked while showing as di

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

https://github.com/i0natan/nodebestpractices/blob/spanish-translation/README.md

@eduardomontalvo - Spanish translation can be officially kicked-off. You're the lead! I'll be at your disposal should you need anything. A branch was created (link below), you should have permissions to it, everyone else must PR before changing anything there.

I would ask/recommend only 2 important guidelines:

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

The Head section says:

The next 2 meta tags (Charset and Viewport) need to come first in the head.

I found a reference for Charset being early on in the head:
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta

The <meta> element declaring the encoding must be inside the <head> element and within the first 1024 bytes of the HTML as some browsers only look at those bytes be