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

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

Preflight Checklist

• I have read the [Contributing Guidelines](https://github.com/electro

In many places in the documentation (example: 'socket' event), socket is not necessarily a net.Socket, but always a stream.Duplex (which net.Socket inherits from). We should at least mention that if we don't want to replace all references.

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

Since this targets 3.7.1, I'm going to close this bug. When class fields reaches stage 4, I'll do the final two steps.

Originally posted by @sandersn in microsoft/TypeScript#27644 (comment)

Provide a quick fix to fix these breaks.

📚 Docs or angular.io bug report

Description

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

Clicking the delete button for an option in the "Multiple Values" and "Fixed Options" examples removes whatever is first in the last.

Expected Behavior 🤔

Clicking the d

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

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

So getAllowedLocations is mentioned in the Atom flight manual, but it's not mentioned elsewhere in the docs. I thought I could implement just getDefaultLocation without having to also implement getAllowedLocations, but I get the following in the developer tools:

`C:\Use

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

Hi, this is a feature request I suppose. The zip file download from the home page is a bit of a 'zip bomb'. I think it would be better to unzip into a contained folder as this can be quite annoying.

Describe the bug
My component define the following property:

items: arrayOf(shape(ITEM_SHAPE)).isRequired,

with the following ITEM_SHAPE definition:

const ITEM_SHAPE = {
    text: string.isRequired,
    value: string.isRequired
};

The rendered prop in docs props table is:

[ { 0: , 1: , 2: , 3: , 4: , 5: , 6: , 7: , 8: , 9: , 10: , 11: , 12: , 13: , 14: , 15

Existing Component

是

Component Name

site

Description

add TOC quick access.

example:
antd
![image](https://user-images.githubusercontent.com/8358236/482508

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

It will be nice to have a document guide to migrate from v0.100.2 to v1.0. Else if it's already there can it be displayed in a more prominent place in the landing page. I had a lot of struggle in migrating my things.