Eslint-Configuration with easy install + es6-es7
Home Page: https://www.npmjs.com/package/eslint-config-equimper
npm i -D eslint-config-equimper eslint || yarn add -D eslint-config-equimper eslint
Create .eslintrc file in the root directory
And paste this code
{
"extends": "equimper"
}
If you want to put the badge in your project.
[](https://github.com/EQuimper/eslint-config-equimper)
![greenkeeper[bot] avatar](https://avatars.githubusercontent.com/in/505?v=4 "greenkeeper[bot]")
| Branch | Build failing 🚨 |
|---|---|
| Dependency | semantic-release |
| Current Version | 15.9.14 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release 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.
The new version differs by 1 commits.
7b8cd99 fix(package): update debug to version 4.0.0See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:
.travis.ymlpackage.json files, so that was left aloneIf 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.
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 🤖
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
6.2.1 to 6.2.2.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 direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 102 commits.
057fb27 6.2.2fc56208 Merge pull request #615 from evcohen/changelog--v6.2.28c5f964 Changelog for v6.2.2f82fbcb Merge pull request #614 from evcohen/update--jsx-ast-utils1c3e63a Update jsx-ast-utils to v2.2.1c571293 Merge pull request #613 from evcohen/add-babel-to-dev-depsc398d3a Add @babel/cli to the dev dependencies13b370c Merge pull request #610 from evcohen/greenkeeper/flow-bin-0.102.0e28b81a Merge branch 'master' into greenkeeper/flow-bin-0.102.0e3163e3 Merge pull request #603 from evcohen/another-attempt-at-eslint-v6f121a78 Merge branch 'master' into another-attempt-at-eslint-v6f3de162 Merge pull request #611 from evcohen/update-jsx-ast-utils91f17be Update ESLint to v61eb9f19 Update jsx-ast-utils to 2.2.0313bc03 chore(package): update flow-bin to version 0.102.0There are 102 commits in total.
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
I love this tool.
This is the problem I have, if I type the following:
import rootReducer from './reducers'
I get this
import rootReducer from './reducers'
; //<----
Is there an option to have the semicolons be added where they should be.
(If there are multiple lines without semicolons, it all works great)
Hi,
It seem the config does not work, I got this error after installing eslint-config-equimper for my react native project:
.../node_modules/eslint-config-equimper/rules/variables.js: Configuration for rule "init-declarations" is invalid: Value "off" no schemas match. Referenced from: equimper Referenced from: ../.eslintrc
I'm using VSCode and ESLint extension by the way.
Best regards,
Hoang
7.12.4 to 7.13.0.This version is covered by your current version range and after updating it in your project the build failed.
eslint-plugin-react is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 74 commits.
f39829f Update CHANGELOG and bump version9e81dde [Deps] update jsx-ast-utils, resolvee73a692 Merge pull request #2256 from mateuszsokola/masterb5fc9bf [fix] jsx-props-no-multi-spaces: support generic components (ts)8bd3837 Fix Node 4 compatibility005dad3 Revert "Replace mocha by jest"6e4f43e Replace mocha by jest09f580c Replace typescript-eslint-parser by @typescript-eslint/parser861fdef [fix] prop-types: fix case with destructuring and defualt param9fbd037 Fix ESLint 6 compat by providing parser as absolute path to RuleTester8041075 Fix jsx-curly-brace-presence schema defaults9cec705 Add next ESLint version to Travis0d4725e Add Node 12 and remove Node 4/6 from Travis9192ec3 Update devDependenciesd5d2e82 Merge pull request #2250 from guliashvili/masterThere are 74 commits in total.
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
So far in my editor I have had errors for:
jsx-a11y/href-no-hashjsx-a11y/label-has-forOpening a PR since I've fixed the first error and will document the fixes in this issue as I run into them. Will push back for merge when completed.
This was the only other culprit. All errors fixed and working with no issues in my current repo. Added comments to commits referencing the docs for each config and why the needed changes were applied. Opening PR for merge.
jsx-a11y/heading-has-content2.16.0 to 2.17.0.This version is covered by your current version range and after updating it in your project the build failed.
eslint-plugin-import is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 61 commits.
0499050 bump to v2.17.0f479635 [webpack] v0.11.18a4226d Merge pull request #1320 from bradzacher/export-ts-namespaces988e12b fix(export): Support typescript namespaces70c3679 [docs] make rule names consistent6ab25ea [Tests] skip a TS test in eslint < 4405900e [Tests] fix tests from #13192098797 [fix] export: false positives for typescript type + value export70a59fe [fix] Fix overwriting of dynamic import() CallExpressione4850df [ExportMap] fix condition for checking if block comment918567d [fix] namespace: add check for null ExportMap2d21c4c Merge pull request #1297 from echenley/ech/fix-isBuiltIn-local-aliases0ff1c83 [dev deps] lock typescript to ~, since it doesn’t follow semver40bf40a [*] [deps] update resolve28dd614 Merge pull request #1304 from bradennapier/feature/typescript-export-typeThere are 61 commits in total.
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | eslint-plugin-import |
| Current Version | 2.3.0 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
eslint-plugin-import is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
The new version differs by 10 commits.
44ca158 update utils changeloga3728d7 bump eslint-module-utils to v2.1.03e29169 bump v2.4.0ea9c92c Merge pull request #737 from kevin940726/master8f9b403 fix typos, enforce type of array of strings in allow option95315e0 update CHANGELOG.md28e1623 eslint-module-utils: filePath in parserOptions (#840)2f690b4 update CI to build on Node 6+7 (#846)7d41745 write doc, add two more testsdedfb11 add allow glob for rule no-unassigned-import, fix #671See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
I am receiving the following error message:
Error: Cannot read config file: /Users/codybrunner/Desktop/photography-frontend/node_modules/eslint-config-equimper/index.js Error: Cannot find module './rules/best-practices' Referenced from: /Users/codybrunner/Desktop/photography-frontend/.eslintrc
Error: Cannot read config file: /Users/codybrunner/Desktop/photography-frontend/node_modules/eslint-config-equimper/index.js
Error: Cannot find module './rules/best-practices'
Referenced from: /Users/codybrunner/Desktop/photography-frontend/.eslintrc
at Function.Module._resolveFilename (module.js:455:15)
at resolve (internal/module.js:27:19)
at Array.map (native)
at Object.<anonymous> (/Users/codybrunner/Desktop/photography-frontend/node_modules/eslint-config-equimper/index.js:13:5)
at Module._compile (module.js:556:32)
at Object.Module._extensions..js (module.js:565:10)
at Module.load (module.js:473:32)
As I'm understanding it looking at the index.js to the module by accessing "extends": "equimper" I am basically getting the eslint config from index.js. The error message is showing that the .map() is failing at the ./rules/best-practices. I'm not quite sure what the require.reslolve is doing so I can't deduce much more from this point.
Is eslint & babel-eslint required as dev-deps in the project directory? I would think not since they are built into your package as dependencies. I have tried removing & adding again, but still get this error. I'm also wondering if the .eslintrc needs to be set up with more than just the "extends" property.
Below are my .eslintrc & package.json:
.eslintrc
{
"extends": "equimper"
}package.json
"dependencies": {
"next": "^2.0.0-beta",
"react": "^15.4.2"
},
"devDependencies": {
"eslint-config-equimper": "^1.0.8"
}A link to the repository I'm using your package in can be found here.
3.0.7 to 3.1.0.This version is covered by your current version range and after updating it in your project the build failed.
commitizen 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.
The new version differs by 2 commits.
26533fc feat(cli): Implement --hook option for git hooks integration (#615)515a57e docs(readme): document behavior of npx git-cz in non-Commitizen friendly repository (#612)See the full diff
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
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.