@fohte/eslint-config
v0.1.1
Published
ESLint config for fohte
Readme
@fohte/eslint-config
Personal ESLint configuration package with TypeScript support.
Installation
npm install @fohte/eslint-configInstallation
npm install --save-dev @fohte/eslint-config
# Install peer dependencies
npm install --save-dev eslint @typescript-eslint/eslint-plugin @typescript-eslint/parser eslint-config-prettier eslint-plugin-import eslint-plugin-simple-import-sort
# Optional: If using TypeScript
npm install --save-dev typescriptUsage
eslint.config.js:
import { mainConfig, typescriptConfig } from '@fohte/eslint-config'
export default [
...mainConfig,
...typescriptConfig,
]Development
Setup
# Install dependencies
npm install
# Build TypeScript
npm run build
# Watch mode
npm run watchScripts
npm run build- Compile TypeScript filesnpm run watch- Watch mode for developmentnpm run lint- Run ESLint on source filesnpm run test- Run build and lint
Project Structure
src/
├── index.ts # Main export
├── main.ts # Base ESLint configuration
├── typescript.ts # TypeScript-specific configuration
└── types/ # Type definitions for untyped packagesRelease Process
This project uses release-please for automated releases.
1. Create a feature branch and make changes
- Create a new branch from
master - Make your changes (commit messages don't need to follow any specific format)
2. Create a PR and merge to master
- Push your branch and create a PR
- PR title must follow Conventional Commits:
fix:for bug fixes (patch release)feat:for new features (minor release)feat!:orfix!:for breaking changes (major release)
- After review, merge the PR (squash merge only)
3. Automated release process
When changes are merged to master, release-please automatically:
- Creates/updates a Release PR
- Updates version in package.json
- Updates CHANGELOG.md
- When the Release PR is merged:
- Creates GitHub release and git tag
- Publishes to npm
Pre-commit Hooks
This project uses pre-commit hooks to ensure code quality. The hooks will automatically run when you commit changes.
