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

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

• The issue is present in the latest release.
• I have searched the [issues](https://github.com/mui

What version of Next.js are you using?

10.1.3, 10.1.4-canary.16

What version of Node.js are you using?

14.15.3

What browser are you using?

Firefox 89.0b3

What operating system are you using?

Ubuntu 18.04.5 LTS

How are you deploying your application?

next export

Describe the Bug

If a page returns { notFound: true } from getStaticProps, th

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

The fix described in issue #20179 introduces a regression, especially from an accessibility perspective. When declaring an empty alt-attribute for an image using the keyword GATSBY_EMPTY_ALT in markdown (![GATSBY_EMPTY_ALT](rel/path.jpg) and having set showCaptions: true in the plugin-options in gatsby-config.js, the plugin produces unwanted HTML:

<figure class="gatsby-resp-i

I'm trying to implement my custom plugin as a native filter but it looks like the height defined for every native filter is 20px, unlike the correct height when the plugin is defined in the dashboard.

Here's the relevant code:
https://github.com/apache/superset/blob/8ef572a4121ffd2fec6f64d0a053218dbf98308a/superset-frontend/src/dashboard/components/nativeFilters/FilterBar/FilterControls/Fi

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

相关平台

H5

浏览器版本: Mozila/5.0 （Linux；Android 9；V1938CT Build/PPR1.180610.011; wv） AppleWebKit/537.36 (KHTML，like Gecko)Chrome/62.0.3202.84 Mobile Safari/537.36 VivoBrowser/8.2.16.1
使用框架: React

复现步骤

在此系统自带的浏览器上, 随机无规律(暂时没找到规律) 部分element显示, 部分element不显示, 刷新后出现的问题也是一致, 在其他手机上(如iphone 6s ios13.3 iphone XSmax 13.6 小米...)

🚀 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

While I try to change header titles by passing array of titles to options like below it does not override the headers. Instead it writes new headers first and original data with old headers again from next cell.

I am experiencing the same problem.

In addition, sheets js is mutating the header array passed in, which is not something I would ever expect.

Example:

const head

🚀 Feature

We should validate docs/blog/pages frontmatter against a Joi schema:

• prevent the user to use bad frontmatter
• display friendly error messages when this happens
• allow unknown frontmatter (user can assign additional metadata to each doc)
• unit-test this validation logic
• try to use the frontmatter TS types in the theme?

Some initial work has been done in https://gith