Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

.eslintrc camelcase configuration error

See original GitHub issue

I currently have the following camelcase rule in my .eslintrc file:

"camelcase": ["error", { "allow": ["^UNSAFE_"] }]

According to the eslint documentation, this is completely valid: https://eslint.org/docs/rules/camelcase#allow

But when I run es6plato I get the following error:

Error: .eslintrc: Configuration for rule "camelcase" is invalid: Value {"allow":["^UNSAFE_"]} should NOT have additional properties.

Is this intended to happen?

Issue Analytics

State:
Created 5 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

Taenickcommented, Mar 19, 2019

@the-simian Thank you!

1reaction

Taenickcommented, Feb 25, 2019

That project is using eslint 5.14.1, which is the latest version according to the npm package site: https://www.npmjs.com/package/eslint

If that feature was just added in august then maybe updating the eslint in the es6plato module will resolve this.

Let me know if there is anything else I should look at.

Top Results From Across the Web

camelcase - ESLint - Pluggable JavaScript Linter

A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.

Disable check of camel case rule in eslint - Stack Overflow

Just get the same camelcase error without any change. The eslint documentation says just disable the entire rule but does not specify a...

camelcase - Rules - ESLint - Pluggable JavaScript linter

This rule looks for any underscores ( _ ) located within the source code. It ignores leading and trailing underscores and only checks...

[@typescript-eslint/camelcase] Use config of ESLint built-in ...

Problem with this approach is that @typescript-eslint/eslint-plugin will use a different configuration as the for the ESLint built-in rules of " ...

eslint/eslint - Gitter

Configuration for rule "camelcase" is invalid: Value {"ignoreDestructuring":true} should NOT have additional properties. Is there an issue with my formatting?