Skip to content

Conversation

@nearlyforget
Copy link

Description

Disable Biome lint to avoid conflicts with ESLint and Stylelint

The build process warns that Biome lint is enabled concurrently with ESLint and Stylelint for various file types (CSS, SCSS, SASS, JS, JSON, JSX, TSX, and Vue), which may cause conflicting rules or redundant checks.

To resolve these warnings, this change disables Biome lint, ensuring that ESLint and Stylelint are the sole linters used for their respective file types.

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)

Is this a Breaking Change or Removal?

No

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

Pull Request Title

This repository enforces Conventional Commits. Your PR title must follow
this format: type: description or type!: description for breaking changes.

Types:

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space,
    formatting, etc)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • chore: Changes to the build process or auxiliary tools and libraries

Breaking Changes:

If your change is a breaking change (e.g., removing a field or file), you
must add ! before the colon in your title:
type!: description

Examples:

  • feat: add new payment gateway
  • fix: resolve crash on checkout
  • docs: update setup guide
  • feat!: remove deprecated buyer field from checkout

No longer needed after the custom CSS is refactored and 'important' keyword is removed.
Disable Biome
@nearlyforget nearlyforget requested a review from a team January 19, 2026 22:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant