I like your project a lot. I've been using it for a couple of months now. Just the demo folder never felt natural for me.
Simplify the project by integrating storybook instead of the demo folder.

then users can create documentation of their components.

I think it will benefit all library authors for React/Preact/ vue/ even javascript.

[Storybook](https://git

https://github.com/shakacode/react_on_rails/blob/master/docs/basics/recommended-project-structure.md

Instead, let's consider recommending leaving package.json and node_modules at the top-level...

There are no big advantages of having this be inside of the /client directory and there are a few additional bits of unnecessary complexity.

@ashgaliyev please add to this discussion.

I use git-bash (like probably nearly all windows npm user).
if i run mkdir -p plop it create me plop folder if not existant and do nothing if it exist.
if i do the same as npm task or with npm-run-all it create me -p folder and plop if they don't exist and fail if there already there.

is'nt possible to use git-bash command in priority when available ?

Tell us about your environment

• ESLint version: 5.9.0
• eslint-plugin-vue version: 6.1.2
• Node version: 10.13.0

Please show your full configuration:

What Renovate type are you using?

I am using Renovate in a private project hosted on Gitlab.com

Describe the bug

It's not a bug but a simple typo. If you start using Renovate, it will usually create a "Pin dependencies" pull request. The PR template contains a

Please leave info about your projects using Cerebral and function tree.
I am prepaing internal presentation on corporate event and I need some cool reference to mention in it. And of course we can include references to your projects on docs website if you want.

Please provide:

• short description
• a link to project if available
• screenshots and/or dynamic gif (especially @gaspard app with

In the Stylistic Issues section, it's mentioned that both URLSearchParams and URL are defined as global variables.

I think this was introduced by this commit nodejs/node@3124146 which match release 10.0.0.

My current runtime is 8.10 (the latest version supported by AWS lambda atm). It seems that this variables were added to the global scope after that

The tap testing framework has improved a lot since we initially started this project. One new(er) addition is official APIs for fixtures.

I'm not 100% exactly which tests need to be refactored, but this seems like a great place for someone to get started if they wanted to contribute

I'm submitting a ... (check one with "x")

[ ] bug report => search github for a similar issue or PR before submitting
[ x] feature request
[ ] support request => Please do not submit support request here, post on Stackoverflow or Gitter

Current behavior
The modal adds a class to the body when it's open and removes it when it closes.

Expected behavior
The class sho

From the docs for no-restricted-disable, it doesn't look like it's possible to do something like this:

{
  "eslint-comments/no-restricted-disable": ["warn", { "level": "error" }]
}

This would allow disabling warnings, but not errors (in

react: 16.9.0 => 16.9.0 
react-native: 0.61.4 => 0.61.4

onColorChange returns a negative value for hue
{ color: { h: -77.86555987333482, s: 69.93991897257706, v: 100 } }

Dashboard content can be implemented like what wordpress used on their dashboard

Contents we can show on the dashboard are:

• Total post (all, published, unpublished, scheduled) *I think content type page not included on this
• List of notification
• Help info (list of text reference with link to documentation repository)
• ... comment or edit to add more

![image](https://user-images.git