Skip to content

fix: Assign configuration object before export in commitlint.config.mjs #241

Closed

Description

@O2sa

Running pnpm lint outputs an ESLint warning: Assign object to a variable before exporting as module default (import/no-anonymous-default-export) in commitlint.config.mjs.

Motivation

Maintaining 0 lint warnings ensures a pristine developer experience and prevents CI noise.

Tasks

  • In commitlint.config.mjs, assign the configuration object to a constant before exporting (e.g., const Configuration = { extends: ['@commitlint/config-conventional'] }; export default Configuration;).
  • Run pnpm lint to verify 0 warnings.
  • Test git commit message validation.

Tip

🚀 Want to contribute?
Comment assign me to be automatically assigned to this issue via our GitHub Actions bot. Happy coding! ✨

Activity

  1. CodeByPeace commented on Oct 12, 2026

    @CodeByPeace
    Contributor

    assign me

    I would like to take this. I will assign the config to a constant before the export, then run pnpm lint and test a commit message before I open the PR.

  2. github-actions commented on Oct 12, 2026

    @github-actions

    🎉 Issue assigned to @CodeByPeace! Happy coding!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions