pure-md5 0.1.14 → 0.2.0

package/.aliases

@@ -0,0 +1,19 @@
+# Detect which `ls` flavor is in use
+if ls --color > /dev/null 2>&1; then # GNU `ls`
+  colorflag="--color"
+else # OS X `ls`
+  colorflag="-G"
+fi
+
+# List all files colorized in long format
+alias ll='ls -lh'
+
+# List all files colorized in long format, including dot files
+alias la="ls -lha"
+
+# List only directories
+alias lsd='ls -l | grep "^d"'
+
+# Always use color output for `ls`
+alias ls="command ls ${colorflag}"
+export LS_COLORS='no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.avi=01;35:*.fli=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.ogg=01;35:*.mp3=01;35:*.wav=01;35:'

package/.bash_profile

@@ -0,0 +1,12 @@
+# Add Homebrew `/usr/local/bin` and User `~/bin` to the `$PATH`
+PATH=/usr/local/bin:$PATH
+PATH=$HOME/bin:$PATH
+export PATH
+
+# Load the shell dotfiles, and then some:
+# * ~/.path can be used to extend `$PATH`.
+# * ~/.extra can be used for other settings you don’t want to commit.
+for file in ~/.{path,bash_prompt,exports,aliases,functions,extra}; do
+  [ -r "$file" ] && source "$file"
+done
+unset file

package/.bash_prompt

@@ -0,0 +1,56 @@
+# @gf3’s Sexy Bash Prompt, inspired by “Extravagant Zsh Prompt”
+# Shamelessly copied from https://github.com/gf3/dotfiles
+# Screenshot: http://i.imgur.com/s0Blh.png
+
+if [[ $COLORTERM = gnome-* && $TERM = xterm ]] && infocmp gnome-256color >/dev/null 2>&1; then
+  export TERM=gnome-256color
+elif infocmp xterm-256color >/dev/null 2>&1; then
+  export TERM=xterm-256color
+fi
+
+if tput setaf 1 &> /dev/null; then
+  tput sgr0
+  if [[ $(tput colors) -ge 256 ]] 2>/dev/null; then
+    # Changed these colors to fit Solarized theme
+    MAGENTA=$(tput setaf 125)
+    ORANGE=$(tput setaf 166)
+    GREEN=$(tput setaf 64)
+    PURPLE=$(tput setaf 61)
+    WHITE=$(tput setaf 244)
+  else
+    MAGENTA=$(tput setaf 5)
+    ORANGE=$(tput setaf 4)
+    GREEN=$(tput setaf 2)
+    PURPLE=$(tput setaf 1)
+    WHITE=$(tput setaf 7)
+  fi
+  BOLD=$(tput bold)
+  RESET=$(tput sgr0)
+else
+  MAGENTA="\033[1;31m"
+  ORANGE="\033[1;33m"
+  GREEN="\033[1;32m"
+  PURPLE="\033[1;35m"
+  WHITE="\033[1;37m"
+  BOLD=""
+  RESET="\033[m"
+fi
+
+export MAGENTA
+export ORANGE
+export GREEN
+export PURPLE
+export WHITE
+export BOLD
+export RESET
+
+function parse_git_dirty() {
+  [[ $(git status 2> /dev/null | tail -n1) != *"working directory clean"* ]] && echo "*"
+}
+
+function parse_git_branch() {
+  git branch --no-color 2> /dev/null | sed -e '/^[^*]/d' -e "s/* \(.*\)/\1$(parse_git_dirty)/"
+}
+
+export PS1="\[${BOLD}${MAGENTA}\]\u \[$WHITE\]at \[$ORANGE\]\h \[$WHITE\]in \[$GREEN\]\w\[$WHITE\]\$([[ -n \$(git branch 2> /dev/null) ]] && echo \" on \")\[$PURPLE\]\$(parse_git_branch)\[$WHITE\]\n\$ \[$RESET\]"
+export PS2="\[$ORANGE\]→ \[$RESET\]"

package/.changeset/README.md

@@ -0,0 +1,32 @@
+# Changesets
+
+This is a monorepo using [Changesets](https://github.com/changesets/changesets).
+
+## Adding a changeset
+
+```bash
+npm run changeset
+```
+
+You will be prompted to:
+
+1. Select which packages to include
+2. Select the type of change (major, minor, patch)
+3. Write a summary of the change
+
+This will create a new file in the `.changeset` directory. Commit this file to your branch.
+
+## Versioning and Publishing
+
+When ready to release:
+
+1. Merge changes to `main` branch
+2. GitHub Actions will create a release PR
+3. Review and merge the release PR
+4. GitHub Actions will publish to npm and create GitHub releases
+
+## Configuration
+
+- **Base Branch**: `main`
+- **Access**: Public
+- **Version Updates**: Patch for internal dependencies

package/.changeset/config.json

@@ -0,0 +1,16 @@
+{
+  "$schema": "https://unpkg.com/@changesets/config@2.3.0/schema.json",
+  "changelog": [
+    "@changesets/changelog-github",
+    {
+      "repo": "eustatos/pure-md5"
+    }
+  ],
+  "commit": false,
+  "fixed": [],
+  "linked": [],
+  "access": "public",
+  "baseBranch": "main",
+  "updateInternalDependencies": "patch",
+  "ignore": []
+}

package/.continue/mcpServers/new-mcp-server.yaml

@@ -0,0 +1,10 @@
+name: ts-language-mcp
+version: 0.0.1
+schema: v1
+mcpServers:
+  - name: ts-language-mcp
+    command: node
+    args:
+      - /Users/aleksanderastashkin/develop/ts-language-mcp/dist/index.js
+      - /Users/aleksanderastashkin/develop/pure-md5
+    env: {}

package/.continue/rules

@@ -0,0 +1,29 @@
+# Project Style Rules
+
+## Language Policy
+
+**All documentation, commits, and comments must be written in English.**
+
+### Commit Messages
+- Use clear, descriptive commit messages in English
+- Follow conventional commit format when applicable:
+  ```
+  feat: add streaming support for large files
+  fix: correct md5 block padding calculation
+  docs: update installation instructions
+  test: add coverage for edge cases
+  ```
+
+### Code Comments
+- Write all comments in English
+- Use clear, descriptive variable and function names
+- Include JSDoc/type descriptions in English for all public APIs
+
+### Documentation
+- Write all documentation in English
+- Include English examples showing expected input/output
+- Keep README files and guides in English
+
+### Pull Requests
+- Describe changes in English
+- Reference issues using proper syntax (e.g., `Fixes #123`)

package/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,35 @@
+---
+name: Bug Report
+about: Create a report to help us improve
+title: "[BUG] "
+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 '....'
+4. See error
+
+**Code Example**
+```javascript
+// Code that reproduces the issue
+```
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Environment:**
+- OS: [e.g. macOS, Windows, Linux]
+- Node.js version: [e.g. 14, 16, 18]
+- Package version: [e.g. 0.1.0]
+- Browser (if applicable): [e.g. chrome, safari]
+
+**Additional context**
+Add any other context about the problem here.

package/.github/ISSUE_TEMPLATE/documentation.md

@@ -0,0 +1,20 @@
+---
+name: Documentation Update
+about: Improve documentation
+title: "[DOCS] "
+labels: documentation
+assignees: ""
+
+---
+
+**Describe what the documentation should cover:**
+A clear and concise description of what topics should be included.
+
+**Current state:**
+What is currently documented?
+
+**Proposed changes:**
+Describe the improvements to the documentation.
+
+**Additional context:**
+Add any other context about the documentation update.

package/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature Request
+about: Suggest an idea for this project
+title: "[FEATURE] "
+labels: enhancement
+assignees: ""
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

package/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,35 @@
+## Description
+Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
+
+Fixes # (issue)
+
+## Type of change
+Please delete options that are not relevant.
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] This change requires a documentation update
+
+## How Has This Been Tested?
+Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
+
+```javascript
+// Test code
+```
+
+**Test Configuration**:
+* Node.js version:
+* OS:
+
+## 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
+
+## Screenshots (if appropriate):

package/.github/workflows/npm-publish.yml

@@ -0,0 +1,33 @@
+# This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
+# For more information see: https://help.github.com/actions/language-and-framework-guides/publishing-nodejs-packages
+
+name: Node.js Package
+
+on:
+  release:
+    types: [created]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: 16
+      - run: npm ci
+      - run: npm test
+
+  publish-npm:
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: 16
+          registry-url: https://registry.npmjs.org/
+      - run: npm ci
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{secrets.npm_token}}

package/.github/workflows/release.yml

@@ -0,0 +1,42 @@
+name: Release
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  release:
+    name: Release
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout Repo
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          
+      - name: Install Dependencies
+        run: npm ci
+      
+      - name: Build
+        run: npm run build
+      
+      - name: Test
+        run: npm test
+      
+      - name: Create Release Pull Request
+        id: changeset
+        uses: changesets/action@v1
+        with:
+          version: npm run ci && npm run changeset:version
+          publish: npm run ci && npm run changeset:publish
+          commit: "chore: update versions"
+          title: "chore: version packages"
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

package/CHANGELOG.md

@@ -0,0 +1,9 @@
+# pure-md5
+
+## 0.2.0
+
+### Minor Changes
+
+- add streaming and some optimization
+
+- add streaming and some optimization

package/CONTRIBUTING.md

@@ -0,0 +1,203 @@
+# Contributing to pure-md5
+
+Thank you for your interest in contributing to pure-md5! 🎉
+
+## Table of Contents
+
+- [Code of Conduct](#code-of-conduct)
+- [How Can I Contribute?](#how-can-i-contribute)
+- [Development Setup](#development-setup)
+- [Running Tests](#running-tests)
+- [Creating Changesets](#creating-changesets)
+- [Pull Request Process](#pull-request-process)
+- [Coding Standards](#coding-standards)
+
+## 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.
+
+## How Can I Contribute?
+
+### Reporting Bugs
+
+Before creating bug reports, please check the existing issues to avoid duplicates. When you create a bug report, please include as many details as possible:
+
+- A clear, descriptive title
+- Steps to reproduce the issue
+- Expected behavior
+- Actual behavior
+- Environment details (OS, Node.js version, package version)
+- Code example that reproduces the issue
+
+### Suggesting Features
+
+Feature requests are welcome! Please provide:
+
+- A clear description of the feature
+- The problem it solves
+- Any alternative solutions you've considered
+- Examples of how the feature would be used
+
+### Pull Requests
+
+1. Fork the repository
+2. Create a feature branch (`git checkout -b feature/amazing-feature`)
+3. Make your changes
+4. Run tests (`npm test`)
+5. Create a changeset (`npx changeset`)
+6. Push your branch (`git push origin feature/amazing-feature`)
+7. Open a Pull Request
+
+## Development Setup
+
+### Prerequisites
+
+- Node.js >= 16
+- npm >= 8
+
+### Installation
+
+```bash
+# Fork the repository first
+git clone https://github.com/eustatos/pure-md5.git
+cd pure-md5
+
+# Install dependencies
+npm install
+
+# Build the project
+npm run build
+
+# Run tests
+npm test
+```
+
+### Available Scripts
+
+| Command | Description |
+|---------|-------------|
+| `npm run build` | Build the project |
+| `npm run build:watch` | Build in watch mode |
+| `npm run build:prod` | Build with minification |
+| `npm run dev` | Run in dev mode |
+| `npm test` | Run all tests |
+| `npm run coverage` | Generate coverage report |
+| `npx changeset` | Create a changeset |
+
+## Running Tests
+
+### All Tests
+
+```bash
+npm test
+```
+
+### Specific Test File
+
+```bash
+npm test __tests__/index.test.ts
+```
+
+### With Coverage
+
+```bash
+npm run coverage
+```
+
+### Watch Mode
+
+```bash
+npm test -- --watch
+```
+
+## Creating Changesets
+
+Changesets are used to manage versioning and changelog generation.
+
+### Creating a Changeset
+
+```bash
+npx changeset
+```
+
+This will prompt you to:
+
+1. Select the version bump type:
+   - `major` - Breaking changes
+   - `minor` - New features
+   - `patch` - Bug fixes
+
+2. Write a description of your changes
+
+### Example
+
+```
+? Which packages would you like to include in this changeset? pure-md5
+? Which type of change is this?
+  patch     Patch release (bug fixes)
+  minor     Minor release (new features)
+  major     Major release (breaking changes)
+```
+
+## Pull Request Process
+
+1. **Update Documentation**: Update README.md or other docs if needed
+2. **Run Tests**: Ensure all tests pass
+3. **Code Review**: Wait for review from maintainers
+4. **Address Feedback**: Make requested changes
+5. **Merge**: Maintainers will merge when approved
+
+### PR Title Format
+
+Use conventional commit format:
+
+```
+type: description
+```
+
+Types:
+- `feat`: New feature
+- `fix`: Bug fix
+- `docs`: Documentation changes
+- `style`: Code style changes
+- `refactor`: Code refactoring
+- `perf`: Performance improvements
+- `test`: Adding tests
+- `chore`: Maintenance tasks
+
+Examples:
+```
+feat: add streaming API for large files
+fix: handle edge case in MD5 calculation
+docs: update installation instructions
+refactor: optimize performance
+```
+
+## Coding Standards
+
+### JavaScript/TypeScript
+
+- Use ES6+ features
+- Follow Airbnb JavaScript Style Guide
+- Use TypeScript for new code
+- Add JSDoc comments for public APIs
+
+### Commit Messages
+
+- Use conventional commits
+- Use present tense
+- Be descriptive but concise
+
+### File Structure
+
+- Place tests in `__tests__/` directory
+- Name test files `<module>.test.ts`
+- Keep files focused on single responsibility
+
+## Questions?
+
+Feel free to open an issue or ask in the pull request if you have questions!
+
+## Acknowledgments
+
+Thank you for contributing to pure-md5! 🙏

package/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2022 eustatos
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+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.