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

Summary

This is task list issue.
"Blocks" fixture app which made by built-in API, 'react-fetch', Server Component combination that useful to play new features v18 later.

But current one is broken because importing removed older Cache API mo

Hi

During the init phase: https://github.com/nodejs/node-inspect/blob/master/lib/internal/inspect_repl.js#L1041

  function initAfterStart() {
    const setupTasks = [
      Runtime.enable(),
      Profiler.enable(),
      Profiler.setSamplingInterval({ interval: 100 }),
      Debugger.enable(),
      Debugger.setPauseOnExceptions({ state: 'none' }),
      Debugger.setAsyncCallS

Node does this
(code tested is https://github.com/denoland/deno/blob/167982be9e7af35e6c12ef6c40c002200bf5e0c0/cli/tests/testdata/error_cause_recursive.ts)

We should do the same

Description

Currently, the Validators.email page explains the email validator logic and talks about the standard that we rely on. However the EmailValidator page, which describes the email validator for template-driven forms doesn't have that info. The proposal is to add a sentence that would

ES imports and exports can only be used at the top level of a module. This is illegal:

function container() {
  import 'fs'
  export { container }
  namespace N { }
}

The current errors for these three statements are vague and, for JS, contain irrelevant terms:

Actual:

(1) "An import declaration can only be used in a namespace or module."
(2) "An export declaration can

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Current behavior 😯

I'm implementing async load with pagination with the Autocomplete.
When the listbox is open and the user scroll to the bottom, we load the next page and add the new options.
After adding, the position of the scroll on the listbox is reseted and

Describe the bug
In Firefox, the zoom feature uses transform styles (see storybookjs/storybook#12845) - unfortunately this breaks positioning on elements that require position: fixed when in the "Docs" view.

Normally a position: fixed element's position would correspond to the viewport but in Firefox it corresponds to the element with the transform style.

Clean up dead or outdated tutorials. Feel free to make a PR.