update 8 files and create 2 files

Author: ioncakephper

.github/ISSUE_TEMPLATE/bug_report.md

@@ -4,14 +4,14 @@ about: Create a report to help us improve
 title: ''
 labels: bug
 assignees: ''
-
 ---
 
 **Describe the bug**
 A clear and concise description of what the bug is.
 
 **To Reproduce**
 Steps to reproduce the behavior:
+
 1. Go to '...'
 2. Click on '....'
 3. Scroll down to '....'
@@ -24,4 +24,4 @@ A clear and concise description of what you expected to happen.
 If applicable, add screenshots to help explain your problem.
 
 **Additional context**
-Add any other context about the problem here.
+Add any other context about the problem here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -20,12 +20,12 @@ Please describe the tests that you ran to verify your changes. Provide instructi
 - [ ] Test A
 - [ ] Test B
 
-## Checklist:
+## 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
+- [ ] New and existing unit tests pass locally with my changes

.gitignore

@@ -1,6 +1,3 @@
-# Dependencies
-/node_modules
-
 # Logs
 logs
 *.log
@@ -9,18 +6,13 @@ yarn-debug.log*
 yarn-error.log*
 lerna-debug.log*
 
-# Diagnostic reports (https://nodejs.org/api/report.html)
-report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json
-
-# Test coverage
-/coverage
+# Dependency directories
+node_modules/
 
-# Build output
-/dist
-/build
+# Coverage directory
+coverage/
 
-# Misc
-.DS_Store
+# Environment variables
 .env
 .env.local
 .env.development.local

CODE_OF_CONDUCT.md

@@ -0,0 +1,121 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+shytiger@yahoo.com
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interaction in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of...
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html

CONTRIBUTING.md

@@ -0,0 +1,126 @@
+# Contributing to js-quality-starter
+
+We welcome contributions to the `js-quality-starter` template! By contributing, you help improve this foundation for JavaScript projects for everyone.
+
+Please take a moment to review this document to understand our contribution guidelines.
+
+## Table of Contents
+
+- Code of Conduct
+- How to Contribute
+  - Reporting Bugs
+  - Suggesting Enhancements
+  - Your First Code Contribution
+  - Pull Request Guidelines
+- Development Setup
+- Code Style
+- Testing
+- Commit Messages
+- License
+
+## Code of Conduct
+
+This project and everyone participating in it is governed by the [js-quality-starter Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to shytiger@yahoo.com.
+
+## How to Contribute
+
+### Reporting Bugs
+
+If you find a bug in the template or its configurations, please open an issue using the Bug Report template.
+
+Before opening a new bug report, please check if a similar issue already exists. When reporting, provide:
+
+- A clear and concise description of the bug.
+- Steps to reproduce the behavior.
+- Expected behavior.
+- Screenshots or code snippets if applicable.
+- Any additional context (e.g., Node.js version, OS).
+
+### Suggesting Enhancements
+
+We're always looking for ways to improve this template! If you have an idea for a new feature or an improvement, please open an issue.
+
+Describe the enhancement, why it would be useful, and provide any relevant examples or mockups.
+
+### Your First Code Contribution
+
+If you're new to contributing to open source or this project, here's a general workflow:
+
+1. **Fork** this repository to your own GitHub account.
+2. **Clone** your forked repository to your local machine:
+
+   ```bash
+   git clone https://github.com/your-username/your-forked-repo.git # Replace with your forked repository URL
+   cd js-quality-starter
+   ```
+
+3. **Install dependencies**:
+
+   ```bash
+   npm install
+   ```
+
+4. **Create a new branch** for your changes:
+
+   ```bash
+   git checkout -b feature/your-feature-name
+   # or bugfix/your-bug-fix-name
+   ```
+
+5. Make your changes.
+6. **Test** your changes (see Testing).
+7. **Commit** your changes (see Commit Messages).
+8. **Push** your branch to your forked repository:
+
+   ```bash
+   git push origin feature/your-feature-name
+   ```
+
+9. Open a **Pull Request** to the `main` branch of the original `js-quality-starter` repository.
+
+### Pull Request Guidelines
+
+When submitting a pull request, please ensure:
+
+- You have read and followed the Pull Request Template.
+- Your branch is up-to-date with the `main` branch of this repository.
+- Your code adheres to the project's Code Style.
+- All existing tests pass, and new tests are added for new features or bug fixes.
+- Your commit messages are clear and follow the Commit Messages guidelines.
+- The PR description clearly explains the problem your PR solves and how it solves it.
+
+## Development Setup
+
+After cloning the repository and running `npm install`, the pre-commit hooks (managed by Husky and lint-staged) will be automatically set up. This ensures that your code is linted and formatted before every commit.
+
+## Code Style
+
+This project enforces code style using ESLint and Prettier.
+
+- `npm run lint`: Checks for linting errors.
+- `npm run lint:fix`: Automatically fixes fixable linting errors.
+- `npm run format`: Checks for formatting issues.
+- `npm run format:fix`: Automatically formats files.
+
+Pre-commit hooks will automatically run `eslint --fix` and `prettier --write` on staged files.
+
+## Testing
+
+Tests are written using Jest.
+
+- `npm test`: Runs all tests.
+
+Please ensure all existing tests pass before submitting a pull request. If you are adding new features or fixing bugs, please include new tests to cover your changes.
+
+## Commit Messages
+
+We encourage the use of Conventional Commits for clear and consistent commit history. Examples:
+
+- `feat: Add new feature for X`
+- `fix: Resolve bug in Y component`
+- `docs: Update README with Z section`
+- `chore: Update dependencies`
+
+## License
+
+By contributing to `js-quality-starter`, you agree that your contributions will be licensed under its MIT License.

LICENSE.md

@@ -1,6 +1,6 @@
-MIT License
+# MIT License
 
-Copyright (c) [year] [fullname]
+Copyright (c) 2025 ioncakephper
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -18,4 +18,4 @@ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+SOFTWARE.