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

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

The styled and wrapped version of the Next.js Linkcomponent provided by the Material UI next-js template/example is not 100% usable in TypeScript projects because IntelliSense does not work with the current JavaScript version of the component. For example, there are no suggestions available for its props.

I converted the JS

Feature request

As a user of [x] framework/language, I'd love to see an easy path towards migrating to Next.js

Describe the solution you'd like

Documentation around common providers and how exactly you can switch to Next.js from them.

Additional context

Let's start with a few of the most popular and see what others in the community would get value from.

• Create React A

Describe the bug
With multiple pure-documentation MDX docs, the scroll position of the preview window does not reset when switching between docs.

To Reproduce
Steps to reproduce the behavior:

1. Create at least two MDX docs without stories, with content long enough to result in a scroll bar.
2. Select the first doc in the sidebar.
3. Scroll down the first document.
4. Select the

Summary

The existing docs about adding Google analytics recommend using the gatsby-plugin-google-analytics. Under the hood, this plugin uses Google's analytics.js file.

However, Google has a guide recommending users upgrade to gtag.js instead. There

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

Is your feature request related to a problem? Please describe.
I have a lot of trouble distinguishing between the shades of green signifying a running vs successful query in sqllab.

Describe the solution you'd like
Ideally these would be two different colors for running vs successful. Maybe yellow and green respectively?

Describe alternatives you've considered
If there isn't

问题描述
最近使用movable-view做了一个拖拽排序的功能，但是由于需要touchmove事件频繁setState来更新movable-view的坐标，导致Android的上的性能体验很差，IOS不会。

看了微信的文档，这种情况可以使用WXS来解决，请问Taro中能否使用WXS？如何使用呢？

参考文档: https://developers.weixin.qq.com/miniprogram/dev/framework/view/interactive-animation.html
https://developers.weixin.qq.com/miniprogram/dev/framework/performance/tips.html

🚀 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

Steps to produce the problem:

1. From https://sheetjs.com/demo/table.html click [Export to XLS!]
2. For comparison, export XLSX and XLSB too.
3. Open the file in Excel 365. In Excel, click [Enable Editing].
4. Ctrl-P to print. ** CRASH **
   OR
5. From https://sheetjs.com/demo/table.html click [Export to XLS!]
6. Open the file in Excel 2010. Excel title bar shows 'compatibility mode'.