Migrate to biome and add lint, typecheck to CI #25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #24
This pull request migrates the project from ESLint and Prettier to Biome for linting and formatting, updates the continuous integration workflow to use Biome and TypeScript type checking, and standardizes TypeScript types and dependencies across packages. It also improves import ordering and code style consistency in several files.
Migration to Biome (Linting & Formatting):
biome.jsonconfiguration file and Biome as a dev dependency inpackage.json, specifying formatting, linting, and ignore rules.package.jsonand.lintstagedrc.json, removing related config and ignore files (.eslintrc.js,.eslintignore,.prettierrc.json,.prettierignore).Continuous Integration Workflow Updates:
.github/workflows/ci.ymlto run Biome linting and TypeScript type checking before tests and build..github/CI.mdto document the new CI steps and local development commands, replacing ESLint/Prettier references with Biome and typecheck steps.TypeScript and Dependency Standardization:
@types/reactand@types/react-domto version^18.2.0in both root andexperience-editorpackage dependencies.These changes modernize the project's code quality tooling, improve developer experience, and ensure consistent formatting and type safety across the codebase.