GithubHelp home page GithubHelp logo

yelp / lemon-reset Goto Github PK

View Code? Open in Web Editor NEW
132.0 7.0 11.0 142 KB

Consistent, cross-browser React DOM tags, powered by CSS Modules. πŸ‹

License: MIT License

Shell 0.06% JavaScript 93.61% Makefile 6.34%

lemon-reset's Introduction

πŸ‹ Lemon Reset

npm Build Status gzip size install size

A set of React components that provide Meyer Reset styles for use with CSS Modules.

For all the DOM tags used in Meyer Reset, Lemon Reset provides a React component with those reset styles, minimizing the effect of browser quirks. In a React world, we prefer components that are self-contained and not reliant on global styling.

Read more about the motivation behind Lemon Reset in our blog post!

Installation

yarn add lemon-reset

Usage

Use these components as a drop in replacement for your existing HTML tags!

import { P } from 'lemon-reset';

ReactDOM.render(<P>Hello World</P>, myContainer);

Wrap Lemon Reset components in your own custom components!

import { Span, Div } from 'lemon-reset';
import styles from './Container.css';

type Props = {
    display: 'inline' | 'inline-block' | 'block' | 'none',
};

const Container = ({ children, display }: Props) => {
    const Tag = display === 'inline' ? Span : Div;
    const classes = styles[`display--${display}`];

    return <Tag className={classes}>{children}</Tag>;
};

export default Container;

Pass in any props! If you need to pass in a ref, you'll need to pass it in as a tagRef:

<Span tagRef={span => console.log(span)}>This has a ref</Span>

Build

Our makefile assumes that you have virtualenv available globally, as we use a python environment for running pre-commit.

If you have virtualenv, simply run:

make build

Otherwise, you can do:

NODE_ENV=production yarn babel src --out-dir lib --copy-files

lemon-reset's People

Contributors

asottile avatar brianokeefe avatar domanchi avatar greenkeeper[bot] avatar jdb8 avatar magicmark avatar mxmul avatar theresama avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

lemon-reset's Issues

An in-range update of eslint-plugin-prettier is breaking the build 🚨

The devDependency eslint-plugin-prettier was updated from 2.6.2 to 2.7.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 3 commits.

  • 869f56d Build: update package.json and changelog for v2.7.0
  • 38537ba Update: Support prettierignore and custom processors (#111)
  • 047dc8f Build: switch to release script package

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

    • The devDependency @babel/cli was updated from 7.4.4 to 7.5.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of react is breaking the build 🚨

Version 16.4.2 of the react packages was just published.

Branch Build failing 🚨
Monorepo release group react
Current Version 16.4.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the react group definition.

react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes v16.4.2

16.4.2 (August 1, 2018)

React DOM Server

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of babel-eslint is breaking the build 🚨

Version 8.2.6 of babel-eslint was just published.

Branch Build failing 🚨
Dependency babel-eslint
Current Version 8.2.5
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

babel-eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 2 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Consider using the new ref forwading API

Currently, we use tagRef to pass along a ref to the actual underlying DOM element

Pass in any props! If you need to [pass in a ref](https://reactjs.org/docs/refs-and-the-dom.html#adding-a-ref-to-a-dom-element), you'll need to pass it in as a tagRef:

Looks like there's a new API to address just this though: https://reactjs.org/docs/forwarding-refs.html

it can be useful for some kinds of components, especially in reusable component libraries

Sounds like us :P

An in-range update of enzyme-to-json is breaking the build 🚨

The devDependency enzyme-to-json was updated from 3.3.4 to 3.3.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

enzyme-to-json is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Some πŸ‹ 0️⃣ usability questions

Had a few questions, figured I'd open them all in an issue :)

  • This provides resets for every element except <body> and <html>: (where they would be)
    • is this intentional?
    • I would guess so, react can't quite produce those elements
    • won't I still need some sort of global reset for these elements?
  • How do I prevent my devs from accidentally using vanilla html elements in react?
    • probably a good opportunity for a pre-commit hook?
  • How do I integrate third party react components?
    • Say I find a totally-sick date picker, do I have to fork and s/div/Div/g in their component?
    • Does this prevent me from taking advantage of out-of-the-box sort of react components?
    • Is this maintenance overhead worth it?
  • Performance?
    • I realize css benchmarks are kind of silly, but has there been any research into whether this approach impacts paint time?
  • Problems with global resets?
    • were there ever any actual problems with a global reset? the blog post hints at potential problems with leaking scope in a .scss file, though I'm not sure how lemon reset helps that -- perhaps it can be elaborated on :)

Thanks! πŸ‘

An in-range update of flow-copy-source is breaking the build 🚨

The devDependency flow-copy-source was updated from 2.0.4 to 2.0.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

flow-copy-source is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of enzyme is breaking the build 🚨

Version 3.4.1 of the enzyme packages was just published.

Branch Build failing 🚨
Monorepo release group enzyme
Current Version 3.4.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the enzyme group definition.

enzyme is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-flowtype is breaking the build 🚨

The devDependency eslint-plugin-flowtype was updated from 3.9.0 to 3.9.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-flowtype is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v3.9.1

3.9.1 (2019-05-23)

Bug Fixes

Commits

The new version differs by 1 commits.

  • 712d840 fix: requireReadOnlyReactProps (#406)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected πŸ€–


FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

SCSS dependency?

It looks like scss compiler is needed for this to run, but it isn't called out anywhere as a dependency. It's a little odd to me that it uses scss under the hood as opposed to just using the compiled CSS, maybe there is a good reason for that. It would be nice if the depency could be removed. If not, a simple note in the description with an example webpack config using SCSS loader would be appreciated.

An in-range update of babel-eslint is breaking the build 🚨

The devDependency babel-eslint was updated from 10.0.1 to 10.0.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

babel-eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v10.0.2

Fixes #772

Commits

The new version differs by 2 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-jsx-a11y is breaking the build 🚨

The devDependency eslint-plugin-jsx-a11y was updated from 6.1.1 to 6.1.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-jsx-a11y is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for Minor fixes and documentation updates

6.1.2 / 2018-10-05
[fix] Add link-type styling recommendation to anchor-is-valid #486
[fix] label-has-for: textareas are inputs too #470

Commits

The new version differs by 12 commits.

  • c538d35 6.1.2
  • ea964b1 Update changelog
  • 43d1d94 Add link-type styling recommendation to anchor-is-valid
  • 71819a0 [Docs] accessible-emoji: plural of emoji is emoji
  • 4a0608b [Docs] label-has-associated-control: update label id
  • 9957219 [Tests] temporarily allow node 4 + eslint 4 to fail
  • 969ce6d [Dev Deps] add missing dev dep
  • 1be1744 [Tests] use nvm install-latest-npm
  • 9103c7a [Tests] add additional test case for #474
  • bbad58a Merge pull request #471 from ljharb/textarea
  • 47633fb [Fix] label-has-for: textareas are inputs too
  • c1bf3c1 Update aria-props.md to link to the correct doc

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-import is breaking the build 🚨

The devDependency eslint-plugin-import was updated from 2.16.0 to 2.17.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-import is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 61 commits.

  • 0499050 bump to v2.17.0
  • f479635 [webpack] v0.11.1
  • 8a4226d Merge pull request #1320 from bradzacher/export-ts-namespaces
  • 988e12b fix(export): Support typescript namespaces
  • 70c3679 [docs] make rule names consistent
  • 6ab25ea [Tests] skip a TS test in eslint < 4
  • 405900e [Tests] fix tests from #1319
  • 2098797 [fix] export: false positives for typescript type + value export
  • 70a59fe [fix] Fix overwriting of dynamic import() CallExpression
  • e4850df [ExportMap] fix condition for checking if block comment
  • 918567d [fix] namespace: add check for null ExportMap
  • 2d21c4c Merge pull request #1297 from echenley/ech/fix-isBuiltIn-local-aliases
  • 0ff1c83 [dev deps] lock typescript to ~, since it doesn’t follow semver
  • 40bf40a [*] [deps] update resolve
  • 28dd614 Merge pull request #1304 from bradennapier/feature/typescript-export-type

There are 61 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

lemon-reset should distribute common-js modules in lib

We currently distribute original sources in ./src/ and transpiled sources (with modules intact) in ./lib. This is fine if you're bundling with Webpack, but means that you can import lemon-reset dom tags in Jest without transpiling things in node_modules.

Let's put fully transpiled sources in ./lib and move the current contents of ./lib to ./es. Then we can specify "module": "es/index.js" in package.json so that Webpack consumes the es sources.

An in-range update of react is breaking the build 🚨

Version 16.3.2 of react was just published.

Branch Build failing 🚨
Dependency react
Current Version 16.3.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v16.3.2

16.3.2 (April 16, 2018)

React

  • Improve the error message when passing null or undefined to React.cloneElement. (@nicolevy in #12534)

React DOM

  • Fix an IE crash in development when using <StrictMode>. (@bvaughn in #12546)
  • Fix labels in User Timing measurements for new component types. (@bvaughn in #12609)
  • Improve the warning about wrong component type casing. (@nicolevy in #12533)
  • Improve general performance in development mode. (@gaearon in #12537)
  • Improve performance of the experimental unstable_observedBits API with nesting. (@gaearon in #12543)

React Test Renderer

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

React does not recognize the tagRef prop on a DOM element

Hi there,

Been using lemon-reset and it's awesome! Thanks for all the amazing work!

Problem is that I'm trying to use the tagRef prop, but am receiving this warning in the console. Is it possible to get this resolved? Thanks!

Warning: React does not recognize the `tagRef` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `tagref` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

An in-range update of prettier is breaking the build 🚨

Version 1.14.0 of prettier was just published.

Branch Build failing 🚨
Dependency prettier
Current Version 1.13.7
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes Prettier 1.14: YAML Support

πŸ”— Release Notes

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-jsx-a11y is breaking the build 🚨

The devDependency eslint-plugin-jsx-a11y was updated from 6.2.1 to 6.2.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-jsx-a11y is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 102 commits.

  • 057fb27 6.2.2
  • fc56208 Merge pull request #615 from evcohen/changelog--v6.2.2
  • 8c5f964 Changelog for v6.2.2
  • f82fbcb Merge pull request #614 from evcohen/update--jsx-ast-utils
  • 1c3e63a Update jsx-ast-utils to v2.2.1
  • c571293 Merge pull request #613 from evcohen/add-babel-to-dev-deps
  • c398d3a Add @babel/cli to the dev dependencies
  • 13b370c Merge pull request #610 from evcohen/greenkeeper/flow-bin-0.102.0
  • e28b81a Merge branch 'master' into greenkeeper/flow-bin-0.102.0
  • e3163e3 Merge pull request #603 from evcohen/another-attempt-at-eslint-v6
  • f121a78 Merge branch 'master' into another-attempt-at-eslint-v6
  • f3de162 Merge pull request #611 from evcohen/update-jsx-ast-utils
  • 91f17be Update ESLint to v6
  • 1eb9f19 Update jsx-ast-utils to 2.2.0
  • 313bc03 chore(package): update flow-bin to version 0.102.0

There are 102 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Lemon reset classes not being rendered

Lemon reset classes are not being rendered on any components in my project. I was very confused by this because I was certain I had already verified v1.1.1 as working, but something has gone sideways since then, which has me horribly confused.

To reduce noise, I've set up a basic create-react-app that reproduces the issue.

https://github.com/am80l/create-react-app-example.git

After setting up create-react-app I then modify the generic app.js to use lemon-reset.

import React, { Component } from 'react';
import logo from './logo.svg';
import './App.css';
import { Div, Header, Img, H1, P } from 'lemon-reset';

class App extends Component {
  render() {
    return (
      <Div className="App">
        <Header className="App-header">
          <Img src={logo} className="App-logo" alt="logo" />
          <H1 className="App-title">Welcome to Hello world!</H1>
        </Header>
        <P className="App-intro">
          To get started, edit <code>src/App.js</code> and save to reload.
        </P>
      </Div>
    );
  }
}

export default App;

As you can see in the screenshot, the classes (and therefore resets) have not been applied.

screen shot 2018-06-15 at 4 40 27 pm

Digging into the React dev tools, we can see that Lemon components are rendering, the stylesheet is also present in the head with the reset class definitions. Every aspect seems to be working, save for the piece that actually puts the lemon class on the html element.

screen shot 2018-06-15 at 4 41 33 pm

screen shot 2018-06-15 at 4 46 53 pm

Any help on this would be greatly appreciated, thank you!

Node Version: v8.11.3
NPM Version: v5.6.0

React Version: 16.0.0
React-Dom Version: 16.0.0

(FYI I also updated to React/React-Dom v16 latest which had no effect on the issue)

typecheck fails with latest version of flow

Bumping flow-bin to latest results in a bunch of type errors:

$ yarn typecheck
yarn run v1.12.1
$ flow check
[2019-01-09 11:20:03.873] Failed to load recheck stats from "/tmp/flow/zSnailzShomezSmmulderzSpgzSlemon-reset.recheck_stats". Reason: "File doesn't exist"
Error β”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆβ”ˆ dist/lemon-reset.js.flow:102:39

Cannot create Tag element because:
 β€’ in property ref:
    β€’ Either HTMLAnchorElement [1] is incompatible with HTMLAudioElement [2] in property current.
    β€’ Or a callable signature is missing in object type [3] but exists in function type [4].
 β€’ in property ref:
    β€’ Either HTMLAnchorElement [1] is incompatible with HTMLCanvasElement [5] in property current.
    β€’ Or a callable signature is missing in object type [3] but exists in function type [4].
 β€’ in property ref:
    β€’ Either HTMLAnchorElement [1] is incompatible with HTMLTableCaptionElement [6] in property current.
    β€’ Or a callable signature is missing in object type [3] but exists in function type [4].
 β€’ in property ref:
    β€’ Either HTMLAnchorElement [1] is incompatible with HTMLDetailsElement [7] in property current.
    β€’ Or a callable signature is missing in object type [3] but exists in function type [4].
 β€’ in property ref:
    β€’ Either HTMLAnchorElement [1] is incompatible with HTMLDivElement [8] in property current.
    β€’ Or a callable signature is missing in object type [3] but exists in function type [4].
 β€’ in property ref:
    β€’ Either HTMLAnchorElement [1] is incompatible with HTMLDListElement [9] in property current.
    β€’ Or a callable signature is missing in object type [3] but exists in function type [4].
 β€’ in property ref:
    β€’ Either HTMLAnchorElement [1] is incompatible with HTMLFieldSetElement [10] in property current.
    β€’ Or a callable signature is missing in object type [3] but exists in function type [4].
 β€’ in property ref:
    β€’ Either HTMLAnchorElement [1] is incompatible with HTMLFormElement [11] in property current.
    β€’ Or a callable signature is missing in object type [3] but exists in function type [4].

An in-range update of flow-typed is breaking the build 🚨

The devDependency flow-typed was updated from 2.5.2 to 2.6.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

flow-typed is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of eslint-config-prettier is breaking the build 🚨

Version 2.10.0 of eslint-config-prettier was just published.

Branch Build failing 🚨
Dependency eslint-config-prettier
Current Version 2.9.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

eslint-config-prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 4 commits.

  • 9f42779 eslint-config-prettier v2.10.0
  • 7a95862 Add more eslint-plugin-react rules
  • becbdf3 Add flowtype/boolean-style
  • 0f13166 Fix wording in readme

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Typo in readme

Nice job on the repo! A small jumped out at me for this code block in the usage section:

import { Span, Div } from 'lemon-reset';
import styles from './Container.scss';

type Props = {
    display: 'inline' | 'inline-block' | 'block' | 'none',
};

const Container = ({ children, display }: Props) => {
    const Tag = display === 'inline' ? Span : Div;
    const classes = styles[`display--${display}`];

    return <Tag className={styles[`display--${display}`]}>{children}</Tag>;
};

export default Container;

Looks like

return <Tag className={styles[`display--${display}`]}>{children}</Tag>;

should be something like

return <Tag className={classes}>{children}</Tag>;

or

return <Tag style={classes}>{children}</Tag>;

Otherwise the classes temp is useless.

An in-range update of eslint-plugin-flowtype is breaking the build 🚨

Version 2.47.0 of eslint-plugin-flowtype was just published.

Branch Build failing 🚨
Dependency eslint-plugin-flowtype
Current Version 2.46.3
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-flowtype is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes v2.47.0

<a name"2.47.0">

2.47.0 (2018-05-22)

Features

  • Refactor array-style-... rules (6320beec)
  • Improve error messages (b95dd31d)
  • Change default array notation for simple types to "verbose" (687f82be)
  • Implement fixation in array style rules (4a6f03d9)
  • Implement array style rules (afd42108)
Commits

The new version differs by 10 commits.

  • 45e86d8 Merge branch 'pnevyk-feat/array-style'
  • 1d664d7 docs: correct documentation
  • a916617 Merge branch 'master' into feat/array-style
  • 8f86c4b docs: add eslint-config-flowtype-essential (#328)
  • 6320bee feat: Refactor array-style-... rules
  • b95dd31 feat: Improve error messages
  • 687f82b feat: Change default array notation for simple types to "verbose"
  • 4a6f03d feat: Implement fixation in array style rules
  • afd4210 feat: Implement array style rules
  • 1232069 docs: Add documentation for array style rules

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-react is breaking the build 🚨

Version 7.11.0 of eslint-plugin-react was just published.

Branch Build failing 🚨
Dependency eslint-plugin-react
Current Version 7.10.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes v7.11.0

Added

Fixed

Changed

Commits

The new version differs by 65 commits.

  • 599c028 Update CHANGELOG and bump version
  • 1eccf7f Merge pull request #1924 from alexzherdev/1775-one-expression-options
  • c1c3d19 Merge pull request #1911 from alexzherdev/1674-prop-types-refactoring
  • 3567c5b [New] Add allow option to jsx-one-expression-per-line
  • 9258d79 Merge pull request #1918 from BenRichter/patch-1
  • bc9a8ea Update jsx-props-no-multi-spaces.md
  • a466a77 Merge pull request #1909 from alexandernanberg/fix/class-property-destructure-assignment
  • 50cd5a6 Clean up and code review
  • 5b5ebfa Made prop-types pass
  • f2fdaa3 Extract declared propTypes detection code
  • 9dbb834 Merge pull request #1914 from alexzherdev/is-function-helper
  • 7edc982 Fix lint error
  • ef36ba9 Add a helper function for determining function-like expressions
  • 4382aa5 fix: destructuring-assignment ignore class properties
  • efe0c0c Merge pull request #1907 from alexzherdev/1637-destructuring-assignment-greedy

There are 65 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of eslint-config-airbnb is breaking the build 🚨

The devDependency eslint-config-airbnb was updated from 17.1.0 to 17.1.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-config-airbnb is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of webpack is breaking the build 🚨

The devDependency webpack was updated from 4.33.0 to 4.34.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v4.34.0

Features

  • Error message when parsing fails shows used loaders now

Bugfixes

  • importing the namespace object from non-ESM (CJS) modules no longer leads to an warning
  • Error message in HMR logging works for Firefox too now
  • Parser understands block scoping now
Commits

The new version differs by 30 commits.

  • 34c8667 4.34.0
  • 0652114 Merge pull request #9268 from webpack/bugfix/let-scopes
  • e6f9db8 Merge pull request #9261 from webpack/bugfix/ff-errors
  • e04b1a5 handle block scopes correctly
  • 55f18f9 Merge pull request #9260 from webpack/fix-9044
  • a1d4567 fix error message and stack in Firefox
  • 8d5ad83 simplify code
  • df5e118 fix(mjs): remove unused namespace build errors
  • acf2c2d Merge pull request #8615 from felixfbecker/patch-1
  • 44fff70 Merge pull request #9256 from webpack/dependabot/npm_and_yarn/@types/node-10.14.9
  • 74178d4 Update snapshot
  • 7fb14ec Add name property to error thrown on chunk load failure
  • 85b0917 chore(deps-dev): bump @types/node from 10.14.8 to 10.14.9
  • 30882ca Link to JS Foundation Code Of Conduct
  • ff85fae Merge pull request #9241 from webpack/dependabot/npm_and_yarn/prettier-1.18.2

There are 30 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of webpack-cli is breaking the build 🚨

The devDependency webpack-cli was updated from 3.3.4 to 3.3.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack-cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for Webpack CLI v3.3.5

Webpack-CLI v3.3.5 has a patch to remove the donation banner that causes some irritation around donations to webpack and for windows users. We've removed this and a full changelog is found here

Commits

The new version differs by 16 commits.

  • 30b1b8d chore: v3.3.5
  • 76b75ac chore: remove donation section
  • 8913928 chore: update pkg lock
  • a37477d cli: remove donation prompt
  • 002a6ac Merge pull request #970 from dhruvdutt/postinstall
  • cd54ba5 chore(scripts): clean opencollective
  • 0c1f6b6 chore(scripts): clean postinstall
  • 313e83e chore(deps): update major versions (#969)
  • 6105ef1 fix(deps): move prettier from dependencies to devDependencies (#968)
  • dad54f4 chore(ts): enables source map in the ts (#961)
  • d7cdab9 Merge pull request #960 from DanielRuf/fix/use-strict
  • 6015bad chore: added await in order to resolve the pending promise (#948)
  • 670efc7 fix: change "usr strict" to "use strict"
  • dc25beb Merge pull request #959 from webpack/fix/deps
  • 69f364e fix: update deps

There are 16 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of optimize-css-assets-webpack-plugin is breaking the build 🚨

The devDependency optimize-css-assets-webpack-plugin was updated from 5.0.1 to 5.0.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

optimize-css-assets-webpack-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 4 commits.

  • eb7de19 5.0.2
  • 110cc11 Upgrade dependency versions
  • 5cdda05 small formatting improvements to README.md (#96)
  • 64f8309 Handle query string in assetName (#82)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-react is breaking the build 🚨

The devDependency eslint-plugin-react was updated from 7.13.0 to 7.14.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v7.14.0

Added

Fixed

  • Fix no-did-mount-set-state and no-did-update-set-state to handle cDU and cDM defined as class properties (#1595 @jaaberg)
  • Fix sort-prop-types cash when a shape PropType is defined in a variable (#1749 @alexzherdev)
  • Fix no-unused-state false positive when using state of non-lifecycle method (#2274 @golopot)
  • Fix static-property-placement false positive when accessing static property inside method (#2283 @dmason30)
  • Fix prop-type detection for annotated props with default value (#2298 @yannickcr)

Changed

Commits

The new version differs by 68 commits.

  • dfaa92f Update CHANGELOG and bump version
  • c52b61b Merge pull request #2316 from kaykayehnn/jsx-key-fragments
  • 8db631b [Fix] Fix detection of annotated props with default value
  • bbebefd [Tests] Remove AppVeyor
  • 0d49f5a [New] Add ESLint ^6.0.0 as valid peerDependency
  • 0364ed2 Fix formatting issues
  • 7c1abed Add checkFragmentShorthand option
  • ed04c2f Fix tests in eslint < 5
  • 0d1aaf8 Handle fragments in jsx-key
  • 7d449a9 [New] jsx-sort-props: Change reported range to only the identifier
  • 1e102f0 Change reported range to only the identifier
  • e6b4c33 Merge pull request #2301 from golopot/fix-cached-props-2
  • 9a63e19 Immediately destructure out propVariables rather than using it as a namespace
  • 3a1a0d1 Apply suggestion: replace mutation with Object.assign
  • 89b8143 Apply suggestion: replace concat([a]) with concat(a)

There are 68 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of eslint-config-airbnb is breaking the build 🚨

Version 17.1.0 of eslint-config-airbnb was just published.

Branch Build failing 🚨
Dependency eslint-config-airbnb
Current Version 17.0.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

eslint-config-airbnb is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.