Bump version to 2.0.24 and add standard files (#68)

* Bump version to 2.0.24 and add standard files

* Update deps

* Okay

---------

Co-authored-by: Denis Tokarev <[email protected]>

Author: github-actions[bot]

.npmignore

@@ -7,6 +7,7 @@ docs/
 lint/
 node_modules/
 src/*
+dist/utils
 
 # Configuration files
 .editorconfig

.npmrc

@@ -0,0 +1 @@
+legacy-peer-deps=true

CODE_OF_CONDUCT.md

@@ -0,0 +1,79 @@
+# 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 [INSERT CONTACT METHOD]. 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 interactions 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 Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 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.
+
+Community Impact Guidelines were inspired by [Mozilla’s code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
+
+[homepage]: https://www.contributor-covenant.org

CONTRIBUTING.md

@@ -0,0 +1,93 @@
+# Contributing to async-wait-until
+
+First off, thank you for considering contributing to async-wait-until! It's people like you that make this project better for everyone.
+
+## Table of Contents
+
+- [Code of Conduct](#code-of-conduct)
+- [Getting Started](#getting-started)
+- [Pull Requests](#pull-requests)
+- [Development Workflow](#development-workflow)
+- [Coding Style](#coding-style)
+- [Testing](#testing)
+- [Reporting Bugs](#reporting-bugs)
+- [Suggesting Features](#suggesting-features)
+- [License](#license)
+
+## Code of Conduct
+
+This project and everyone participating in it is governed by our Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to the project maintainers.
+
+## Getting Started
+
+### Prerequisites
+
+- Node.js (version specified in package.json)
+- npm or yarn
+
+### Setup
+
+1. Fork the repository
+2. Clone your fork: `git clone https://github.com/YOUR-USERNAME/async-wait-until.git`
+3. Navigate to the project directory: `cd async-wait-until`
+4. Install dependencies: `npm install` or `yarn install`
+5. Create a new branch for your changes: `git checkout -b feature/your-feature-name`
+
+## Pull Requests
+
+1. Ensure your code passes all tests
+2. Update documentation if necessary
+3. Include relevant tests for your changes
+4. Ensure your commits are well-formatted and descriptive
+5. Submit a pull request to the `main` branch
+
+### Pull Request Process
+
+1. Update the README.md with details of changes if applicable
+2. Increase the version numbers in package.json and other relevant files following [Semantic Versioning](https://semver.org/)
+3. The PR will be merged once it has been reviewed and approved by a maintainer
+
+## Development Workflow
+
+1. Make your changes
+2. Run tests: `npm test` or `yarn test`
+3. Lint your code: `npm run lint` or `yarn lint`
+4. Fix any issues before committing
+
+## Coding Style
+
+- This project uses ESLint and Prettier for code formatting
+- Follow the existing code style
+- Use descriptive variable and function names
+- Add comments for complex logic
+
+## Testing
+
+- Write tests for new features and bug fixes
+- Ensure all tests pass before submitting a PR
+- Aim for good test coverage
+
+## Reporting Bugs
+
+When reporting bugs, please include:
+
+- A clear and descriptive title
+- Steps to reproduce the issue
+- Expected behavior
+- Actual behavior
+- Environment information (OS, Node.js version, etc.)
+- Any relevant logs or screenshots
+
+## Suggesting Features
+
+When suggesting features:
+
+- Clearly describe the feature and its benefits
+- Provide examples of how it would be used
+- Indicate if you're willing to help implement it
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the same license as the project.
+
+Thank you for contributing to async-wait-until!

README.md

@@ -7,6 +7,10 @@ A lightweight, zero-dependency library for waiting asynchronously until a specif
 ![MIT License](https://img.shields.io/npm/l/async-wait-until)
 [![Maintainability](https://api.codeclimate.com/v1/badges/2a967399786c0d306247/maintainability)](https://codeclimate.com/github/devlato/async-wait-until/maintainability)
 
+## 📖 Detailed Documentation
+
+For detailed documentation, visit [https://devlato.github.io/async-wait-until/](https://devlato.github.io/async-wait-until/)
+
 ---
 
 ## 🚀 Installation
@@ -122,3 +126,11 @@ Contributions are welcome! To contribute:
 - **Generate Docs:** `npm run docs`
 
 ---
+
+## 📝 Links
+
+- [License](./LICENSE)
+- [Detailed Documentation](https://devlato.github.io/async-wait-until/)
+- [Changelog](./CHANGELOG.md) - Track version updates and changes
+- [Contributing Guidelines](./CONTRIBUTING.md) - How to contribute to the project
+- [Code of Conduct](./CODE_OF_CONDUCT.md) - Community standards and expectations