akameco / eslint-config-precure

ESLint shareable config for precure

eslint-config-precure

ESLint shareable config for me

Features

• prettier
• React
• TypeScript
• flowtype (maintenance mode)

Install

$ yarn add --dev eslint eslint-config-precure

$ npm install --save-dev eslint eslint-config-precure

Usage

.eslintrc

{
  "extends": "precure"
}

TypeScript

{
  "extends": ["precure", "precure/typescript"]
}

Jest

{
  "extends": ["precure", "precure/jest"]
}

Auto Config

if you use typescript, enable typescript-eslint

if you use jest, enable eslint-plugin-jest

if you use react, enable eslint-plugin-react

if you use flow-bin, enable eslint-plugin-flowtype

{
  "extends": "precure/auto"
}

Contributors

Thanks goes to these wonderful people (emoji key):

akameco 💻 📖 ⚠️ 🚇

bsky 💻

This project follows the all-contributors specification. Contributions of any kind welcome!

License

MIT © akameco

eslint-config-precure's Issues

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Update Dependencies (Renovate Bot)

This repository is up-to-date and has no outstanding updates open or pending.

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.