# Support

Use this guide to choose the right support path for
`eslint-config-nick2bad4u`.

## Where to ask

| Request                            | Where to go                                                                       |
| ---------------------------------- | --------------------------------------------------------------------------------- |
| Bug report                         | Open a GitHub issue in the repository issue tracker.                              |
| Feature request or preset proposal | Open a GitHub issue with the use case and expected config behavior.               |
| Documentation problem              | Open a GitHub issue or pull request that identifies the stale or missing section. |
| Security concern                   | Follow the private reporting process in the [security policy](./SECURITY.md).     |

Issue tracker: [Nick2bad4u/eslint-config-nick2bad4u issues](https://github.com/Nick2bad4u/eslint-config-nick2bad4u/issues)

## Before opening an issue

Include enough context for maintainers to reproduce the problem without guessing:

- `eslint-config-nick2bad4u` version;
- Node.js and npm versions;
- ESLint and TypeScript versions;
- operating system and shell;
- minimal `eslint.config.mjs`;
- relevant `tsconfig.eslint.json`;
- command you ran;
- complete error output or a focused excerpt that includes the first failure;
- whether the issue still happens after reinstalling dependencies from a clean
  lockfile.

## Scope of support

Maintainers can help with package bugs, stale documentation, migration issues,
peer dependency problems, and shared-config behavior. Project-specific rule
preferences may be declined unless they fit the shared Nick2bad4u plugin
repository baseline.

For sensitive reports, do not include proof of concept details in a public issue.
Use the [security policy](./SECURITY.md) instead.