React version: 17.0.1 (latest)

Steps To Reproduce

This code finishes properly in node.js 14, but holds the process open in node.js 15

global.window = global; // simulate JSDOM
require('scheduler');

Since node.js 15, there is a global MessageChannel object now, which prevents node event loop from exiting. To let the process shut down properly, it should either call `po

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 version of Next.js are you using?

10.0.6-canary.9

What version of Node.js are you using?

14.15.4

What browser are you using?

Firefox 84

What operating system are you using?

Ubuntu 20.04

How are you deploying your application?

Vercel

Describe the Bug

Recently (i think 10.0.6-canary.8) the behavior for shallow routing was changed to not scroll-to-top anymore

The search input on the left nav is working correctly but I think still some bugs in the custom theme configuration.

The switch buttons under control it's taking the toolbar background.

The arrows in the left nav on hover, focus,

Currently, the user's scroll position is stored within session storage, and this is violating a GDPR compliance check (yes, I know). Is there a way to disable this storage?

Screenshot

Description

There needs to be some space between the run buttons and the validation error indicator. (You see this indicator when there are frontend validation errors, which can happen when you create a new bar cha

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

相关平台

环境信息

Taro CLI 3.0.7 environment info:
    System:
      OS: macOS

🚀 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

a nice tip from Mark dalgleish: https://twitter.com/markdalgleish/status/1339863859469955072?s=20

I have no idea where to put this, let me know if you have an idea

🐛 Bug Report

Plugins must be paths. If they are functions they are just ignored silently.

Have you read the Contributing Guidelines on issues?

Yes.

To Reproduce

plugins.push(customWebpackPlugin)

function customWebpackPlugin(context, options) {
  console.log('hi')
  retu