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

Describe the feature you'd like to request

A --skip-install option in create-next-app, like in react-native, to skip installing dependencies would be really great. It allows using other package managers like pnpm

Describe the solution you'd like

do not install dependencies automatically when the --skip-install option is set. But the dependencies should be listed in package.json,

• 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

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

• Chrome version:
  • 95.0.4638.54 (Official Build) (64-bit) (ubuntu)
  • 95.0.4638.54 (Official Build) (64-bit) (windows)
  • 94.0.4606.85 (Official Build) (Android 1

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 directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Description

I j

Screenshot

I've added a red vertical ruler so that you see the issue

Description

As already explained in numerous issues, the use of 'Inter' font is problematic, it does not allow to align dates for instance,
and does not play nice with numbers either.

In my supe

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

Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

Description

The "docs-only" and "blog-only" names are confusing, because they just change the routing path but don't prevent you from using other plugins. Moreover, the instructions ar

Hi,

I'm currently on the version ^0.17.0

I'm having trouble with the function writeFile containing some sheets with more than 256 columns. The others columns are not present in the document and no error is throwing.

I didn't find any documentation on it.

This is due to a limitation of the library ? Maybe add a warning in this case ?