-
Updated
Apr 23, 2021 - JavaScript
React
React (also known as React.js or ReactJS) is a JavaScript library that makes developing interactive user interfaces simple.
Here are 135,142 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
Mar 25, 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.1.3
What version of Node.js are you using?
v14.16.1
What browser are you using?
Safari
What operating system are you using?
macOS
How are you deploying your application?
Vercel
Describe the Bug
Debugging a starter Next.js installation shows several warnings. Even if they are benign, they make it hard to notice other warni
What's the problem?
I have successfully customized my storybook with addon-themes and created the dark style for div with a .docs-story class.
I tried to style the "show code" button on the docs tab without luck via CSS in preview-head.html.
The problem is that there is no unique CSS class to scope (only dynamically generated classes):
<div class="css-11xgcgt">
<button c
-
Updated
Apr 22, 2021 - TypeScript
-
Updated
Apr 22, 2021
-
Updated
Apr 19, 2021 - JavaScript
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
-
Updated
Sep 4, 2020 - CSS
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).
 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 小米...)
Taro能使用wxs吗?
-
Updated
Apr 19, 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
Apr 13, 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
Apr 22, 2021 - JavaScript
-
Updated
Apr 23, 2021 - Go
-
Updated
Apr 22, 2021 - TypeScript
-
Updated
Apr 23, 2021 - JavaScript
🚀 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
Created by Jordan Walke
Released March 2013
Latest release about 1 month ago
- Repository
- facebook/react
- Website
- reactjs.org
- Wikipedia
- Wikipedia
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