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

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a featu

With the introduction of web streams, it would be good to integrate support into the various common stream utilities...

Refs: nodejs/node#39134

/cc @mcollina @ronag

• stream.finished()

const { finished } = require('stream');
finished(new ReadableStream(), (err) => { /* ... */ });
finished(new WritableStream(), (err) => { /* ... */ });
finished(new Tr

See https://github.com/denoland/deno/blob/main/ext/web/08_text_encoding.js#L98.

Currently for a non streaming decode we perform 3 native calls:

• op_encoding_new_decoder to create the decoder
• op_encoding_decode to actually perform the decoding
• core.close to destroy the decoder

For cases where options.stream === false this can be reduced to a single decode op.

To do this,

Description

The issue is described here

You cannot possibly be held responsible for all contingencies for every system, that would be unreasonable. However, it would benefit the community, especially those of newcomers, were this issue at least mentioned as known in your docs. A timestamped solution would be

TS Template added by @mjbvz

TypeScript Version: 4.5.0-dev.20211028

Search Terms

• javascript
• checkjs
• strict

See microsoft/TypeScript#46570 (comment) for more minimal repro

In minimal-hello-world extension sample, using this code:

// The module 'vscode' contains the VS Code extensibility API
// Import the module and

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.