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

React version: 17.0.1

Steps To Reproduce

1. npx create-react-app my-app
2. cd my-app
3. npm start (Works like a charm)
4. npm run eject
5. npm i
6. npm start (ReferenceError: React is not defined)

Link to code example: https://codesandbox.io/s/ecstatic-wood-ou6px

What example does this report relate to?

from-docker

What version of Next.js are you using?

latest

What version of Node.js are you using?

node:16-alpine

What browser are you using?

chrome

What operating system are you using?

macOS

How are you deploying your application?

sudo docker build -t myappname .

Describe the Bug

trace :

• I have searched the issues of this repository and believe that this is not a duplicate.

Reproduction link

Steps to reproduce

• Open demo at https://ant.desig

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.

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
• This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Summary

I am working on a source plugin an

Is your feature request related to a problem? Please describe.

Since SIP-9 in 2018, TypeScript has been a part of the Superset repo. Since SIP-36 in 2020 all new frontend code should be written in TypeScript. When modifying old functions/components, migrating to TypeScript is appreciated, but n

We are currently adding Hyper CLI path to user PATH in Windows registry: https://github.com/zeit/hyper/blob/262eb8ad9b7b9b15351f331765151538d67a09e2/app/utils/cli-install.js#L49-L91

A caveat is that environment variables are cached and users should open and validate "Edit environment variables for your account" dialog to force a cache refresh (or simply reboot their workstation).
![](https://

(If applicable) Reproduction of issue in TypeScript Playground

start with the basic TS + React template

相关平台

微信小程序

复现仓库

https://github.com/yangxudong-functorz/taro_issues/blob/main/issue1.ts
小程序基础库: 2.17.3
使用框架: React

复现步骤

直接只用 npm run build:weapp, 报错: Module not found: Can't resolve '"},"path":"....../xxx.config.ts"

期望结果

编译成功

🚀 Feature

Front matter should accept both a simple option:

``

🚀 Feature request

Current Behavior

The type ErrorMessage doesn't have an id property.

Desired Behavior

It'd be nice id?: string would be added to the type ErrorMessage and set on the outermost component that serves as error message.

Suggested Solution

Add id={this.props.id} to the outer component in ErrorMessage.

Who does this impact? Who is this

I'm trying to migrate from PHPOffice/PhpSpreadsheet to this package. PhpSpreadsheet works fine with my xlsx file, while sheetjs gives no info about hidden rows. It's really important since my script needs to ignore hidden cells.

Mentioned file has been sent to email from the Contributing doc.

Package version: "xlsx": "^0.17.4".