Question 1

How to use eslint-plugin-unicorn with TypeScript?

Accepted Answer

Integrate it by adding the plugin to your ESLint configuration and ensuring TypeScript parser settings are compatible. The plugin works with TypeScript, but you might need to adjust some rules for type-specific contexts or use additional ESLint plugins for TypeScript.

Question 2

eslint-plugin-unicorn vs eslint-config-standard: which is better for modern JavaScript?

Accepted Answer

eslint-plugin-unicorn focuses on advanced error prevention and modern syntax enforcement, while eslint-config-standard is a broader style guide. Use Unicorn on top of a base config like Standard for comprehensive linting aimed at cutting-edge practices.

Question 3

Why does eslint-plugin-unicorn forbid using null?

Accepted Answer

The 'no-null' rule discourages null in favor of undefined to simplify code and avoid common pitfalls like type coercion issues. However, this can be disabled in your config if your project relies on null for interoperability or semantic reasons.

Question 4

Can I run eslint-plugin-unicorn on a CommonJS project?

Accepted Answer

Yes, but it requires ESLint's flat config and ESM setup, which might involve migration efforts. Some rules like 'prefer-module' will enforce ES modules, so you may need to disable or configure them to avoid conflicts.

Question 5

How to disable a specific rule in eslint-plugin-unicorn?

Accepted Answer

In your ESLint configuration file, set the rule to 'off' or 'warn' instead of 'error'. For example, add 'unicorn/no-null': 'off' to your rules object to allow the use of null while keeping other rules active.

Unicorn

What is Unicorn?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions