-
Updated
Feb 18, 2021 - JavaScript
React
React (also known as React.js or ReactJS) is a JavaScript library that makes developing interactive user interfaces simple.
Here are 125,604 public repositories matching this topic...
React version: 17.0.1
Steps To Reproduce
- npx create-react-app my-app
- cd my-app
- npm start (Works like a charm)
- npm run eject
- npm i
- npm start (ReferenceError: React is not defined)
Link to code example: https://codesandbox.io/s/ecstatic-wood-ou6px
-
Updated
Feb 16, 2021
- 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.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
Is your feature request related to a problem? Please describe
I am writing cypress tests for my Storybook documentation, and have leveraged control ids for boolean and radio controls. But I have noticed for other control types these ids are not generated
As an example for radio buttons each input is given the id {controlName-optionName}, which is nice and predictable
A couple of control
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?
-
Updated
Feb 18, 2021 - TypeScript
-
Updated
Feb 18, 2021
-
Updated
Sep 4, 2020 - CSS
-
Updated
Jan 21, 2021 - JavaScript
BigQuery error is hard to read.
Expected results
In Explore, when creating a bad expression (say DATE_TRUNC(column_that_dont_exist, DAY)) in BigQuery, the DatabaseError is shown as a UnknownError. In SQL Lab, DatabaseErrors are surfaced properly and make sure to use a monospace font so that the formatting is preserved. For most database, the formatting doesn't matter much, but for BigQ
any plans for a Linux ARM build? if nobody else is on it or has attempted it, i can give it a try.
-
Updated
Feb 9, 2021 - JavaScript
-
Updated
Feb 11, 2021 - JavaScript
-
Updated
Feb 18, 2021 - JavaScript
-
Updated
Feb 16, 2021 - TypeScript
-
Updated
Feb 18, 2021
相关平台
微信小程序
复现仓库
https://github.com/li-z/taro-bug
小程序基础库: 2.12.0
使用框架: React
复现步骤
运行项目后点击跳转到详情页,然后返回首页。然后触发子组件的 onClick 事件时,回调函数却还是详情页的函数。去掉id属性后正常。
期望结果
有无id属性都应正常
实际结果
有id属性异常
环境信息
Taro CLI 3.0.7 environment info:
System:
OS: macOS
Taro能使用wxs吗?
-
Updated
Feb 15, 2021 - JavaScript
🚀 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
-
Updated
Feb 16, 2021
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-
Updated
Jan 12, 2021 - JavaScript
-
Updated
Feb 18, 2021 - TypeScript
-
Updated
Jan 26, 2021 - JavaScript
-
Updated
Nov 9, 2020 - JavaScript
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')
retuCreated by Jordan Walke
Released March 2013
Latest release 4 months ago
- Repository
- facebook/react
- Website
- reactjs.org
- Wikipedia
- Wikipedia
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
Since node.js 15, there is a global
MessageChannelobject now, which prevents node event loop from exiting. To let the process shut down properly, it should either call `po