Document Classifier Component Development

Development instructions for working with the document classifier component codebase (ilb/classifiercomponent).

Project Overview

This is a React-based document classifier component built with Next.js. The project uses modern JavaScript/JSX with ESLint and Prettier for code quality.

Available Commands

When working with this codebase, use these npm scripts:

**Development:**

**Code Quality:**

**Testing:**

Code Style Requirements

Follow these strict style guidelines when writing or modifying code:

Formatting Rules

Naming Conventions

File Extensions

Error Handling

Step-by-Step Workflow

1. Starting Development

```bash

npm run dev

```

Navigate to `http://localhost:3010` to view the application.

2. Making Code Changes

Before editing:

1. Read existing code to understand patterns

2. Check `Errors.mjs` for error handling conventions

3. Review component structure for consistency

When writing code:

1. Use appropriate file extensions (`.js`/`.mjs`)

2. Follow naming conventions strictly

3. Apply ESLint/Prettier rules automatically

3. Code Quality Checks

Before committing:

```bash

Check for linting issues

npm run lint

Auto-fix fixable issues

npm run lint:fix

```

4. Testing Changes

Run relevant tests:

```bash

npx jest path/to/test/file.test.js

```

5. Building for Production

```bash

npm run build

npm run start

```

Verify build succeeds without errors.

Important Constraints

Common Tasks

Adding a New Component

1. Create file with `.js` extension in appropriate directory

2. Use PascalCase for component name

3. Follow existing component structure

4. Import and use error patterns from `Errors.mjs`

5. Run linter before saving

Debugging

1. Check browser console for client-side errors

2. Check terminal output for server errors

3. Review error messages from `Errors.mjs`

4. Use `npm run dev` for hot reloading during debugging

Modifying Server Code

1. Use `.mjs` extension for new server files

2. Follow existing patterns in server-side code

3. Test with `npm run build` before deploying