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

PR #19108 caused some Suspense-related DevTools regressions (more info available on #19368) which we did not catch because of the fact that DevTools tests are only run against the version of React in master.

We should follow the precedent of the regression fixtures tests and have CI run DevTools tests against multiple

Preflight Checklist

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

It might be possible to have a more efficient way to pipe a file to a stream by adding a .stream method to FileHandle.

e.g.

FileHandle.prototype.stream = async function (dst, { start = 0, end, signal } = {}) {
 // TODO: this[kRef](), this[kUnref](), if (signal.aborted) throw AbortError()
  let pos = start
  while (true) {
    if (end && pos >= end) {
      break
    }
  

Deno strives to be browser compatible where possible; that means we use quite a few Web APIs.

There is not much docs for supported Web APIs at the moment and before 1.0 is released that situation must change. Some of APIs and not fully aligned to spec, while others are not fully implemented (#3557). All that knowledge should be written down and presented to end users to avoid multiple question

🐞 bug report

Affected Package

The issue is caused by package @angular/common.

Is this a regression?

No.

Description

This is a request for clearer error messaging. When an NgSwitchDefault directive erroneously exists

If we do #43710, the first thing you'll see every time you request completions on a string is a bunch of crossed-out properties. Ideally, we never would've shown these properties anyway, but we traditionally had to have them there because ES6.

Originally posted by @DanielRosenwasser in microsoft/TypeScript#43710 (comment)

__

@deprecated has its o

When using the Autocomplete component with the freeSolo option, the onClose is called with reason 'create-option' when creating a new option. However the 'create-option' reason is not present in the AutocompleteCloseReason type, causing TypeScript warning.

• The issue is presen

Describe the bug
When story id starts with settings, the addon panel is frozen/broken/not responding. 🤯

https://user-images.githubusercontent.com/11510581/116053981-83f51f80-a67b-11eb-8a70-28e8b989b50e.mp4

To Reproduce
I reproduced it on newly created CRA with SB. See video above.

To reproduce: just add story id starting with settings

export default {
  title: "