When react is inside an iframe, chrome extension for react devtools fails to detect react.

This is because the extension sets `REACT_DEVTOOLS_GLOBAL_HOOK

This is a good first PR!

We should add some tests to cover #7036. They should cover both JavaScript and TypeScript support.

They can probably be added to test/fixtures.

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

Reproduction link

Steps to reproduce

Project Too Large to isolate

What is exp

I'm not sure what the policy on css transitions is in this repo, but here's a suggestion.

I noticed that color transitions on the StepIcon component are instantaneous, even though the entire component is quite animated and fluid. The StepIcon goes through several colors (default -> active -> completed), and I believe a simple transition: color 300ms ease; already adds quite a bit more style

Describe the bug
Creating angular project with no initial app throws sb init error
• Detecting project type. ✓
• Adding Storybook support to your "Angular" app
TypeError: Cannot read property 'architect' of undefined

To Reproduce
Steps to reproduce the behavior:

1. ng new ng-ui --create-application=false
2. cd ng-ui
3. ng g lib button -p ui
4. npx -p @storybook/cli sb

Bug report

Describe the bug

When using v9.5.2 on ionic webview,
next/router not working at all,

• Router.push('/login')
• <Link href="/login">

No error message
No response to click

The ionic webview is using ionic://localhost/,
maybe v9.5.2 unable to working on ionic://localhost/.

To Reproduce

I hope the description enough to explain where are the problem,

Summary

Where: https://www.gatsbyjs.org/docs/ssr-apis/#onRenderBody

What: Improve the example for onRenderBody or add another example, simple, that is not tied to a plugin.

Suggestion

// Object of props
const HtmlAttributes = {
  "data-whatever": "content"
}

// Magic
exports.onRenderBody = (
  { setHtmlAttributes }
) => {
   setHtmlAttributes(HtmlAttributes)
}

any plans for a Linux ARM build? if nobody else is on it or has attempted it, i can give it a try.

At some point we moved from using mocha as a test runner to using jest, and jest out of the box started reporting much more warnings than mocha did.

No one went to clean up this output. In many cases it may just be about passing an extra prop in a component or setting a proper default value for a component's prop, or adding up to an existing fixture.

[optional] please roll out in chu

相关平台

微信小程序

小程序基础库: 2.12.0
使用框架: React

复现步骤

组件库是 vant-weapp (所有组件的 slots 都无法使用）

<van-calendar
  show={visible}
  show-confirm
  type="range"
  defaultDate={[new Date().getTime() - (7 * 24 * 3600 * 1000), new Date().getTime()]}
  onClose={onClose}
  onConfirm={(e) => onConfirm(e)}
  >
  <slot name=

🚀 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

Since version 0.16.5, th following code returns a null worksheet:
XLSX.utils.json_to_sheet([], {header: columns})

Is it now working as it is wanted? If so, how could we create an empty worksheet? In my case it is expected that sometimes the data is an empty array. And an empty worksheet only with headers is expected.