almighty-tool 0.0.113 → 0.0.115

package/.opencode/skills/cryptography-dev.md

@@ -1,108 +1,108 @@
----
-description: Cryptography and security implementation for WeChat Mini Programs
-mode: skill
----
-
-**Skill Name**: Cryptography Implementation with WeChat Mini Program Support
-
-**Expertise**: Cryptography, security, WeChat Mini Program compatibility, JavaScript/TypeScript
-
-**Technology Stack**:
-
-- **Primary Libraries**: crypto-js, jsencrypt
-- **Prohibited**: node-forge (not compatible with WeChat Mini Programs)
-- **Hash Algorithms**: MD5, SHA1, SHA256, SHA384, SHA512
-- **Encryption**: AES (CBC, CTR, GCM, ECB modes)
-- **Asymmetric**: RSA with jsencrypt
-
-**Implementation Guidelines**:
-
-1. **Library Selection**:
-
-   - ✅ Use `crypto-js` for symmetric encryption and hashing
-   - ✅ Use `jsencrypt` for RSA operations
-   - ❌ Never use `node-forge` (incompatible with WeChat Mini Programs)
-
-2. **WeChat Mini Program Compatibility**:
-
-   - All cryptography must work in browser environment
-   - No Node.js-specific APIs or dependencies
-   - Test in simulated WeChat Mini Program environment
-
-3. **Best Practices**:
-
-   - Use appropriate key sizes (AES-256, RSA-2048+)
-   - Implement proper IV/nonce generation
-   - Use secure random number generation
-   - Avoid hardcoded keys and secrets
-
-4. **Common Use Cases**:
-   - Password hashing (with salt)
-   - Data encryption at rest
-   - Secure data transmission
-   - Digital signatures
-   - Key generation and management
-
-**Code Patterns for almighty-tool**:
-
-1. **Hash Functions**:
-
-   ```typescript
-   // crypto-js pattern
-   import CryptoJS from 'crypto-js';
-   const hash = CryptoJS.SHA256('data').toString(CryptoJS.enc.Hex);
-   ```
-
-2. **AES Encryption**:
-
-   ```typescript
-   const encrypted = CryptoJS.AES.encrypt(data, key, {
-     iv: iv,
-     mode: CryptoJS.mode.CBC,
-     padding: CryptoJS.pad.Pkcs7,
-   });
-   ```
-
-3. **RSA Operations**:
-   ```typescript
-   import JSEncrypt from 'jsencrypt';
-   const jsEncrypt = new JSEncrypt();
-   jsEncrypt.setPublicKey(publicKey);
-   const encrypted = jsEncrypt.encrypt(data);
-   ```
-
-**Testing Requirements**:
-
-- All crypto operations must be tested with `bun test`
-- Verify compatibility with existing test cases
-- Test edge cases (empty strings, null values, large data)
-- Ensure deterministic output for same inputs
-
-**Security Considerations**:
-
-- Never log sensitive data (keys, passwords, plaintext)
-- Use proper error handling for crypto failures
-- Validate input data before crypto operations
-- Follow cryptographic best practices
-
-**File Locations in Project**:
-
-- Main crypto utility: `src/utils/crypto.util.ts`
-- Test file: `tests/unit/utils/crypto.util.spec.ts`
-- Dependencies: `package.json` (crypto-js, jsencrypt)
-
-**Common Issues to Avoid**:
-
-- Using deprecated algorithms (MD5 for passwords)
-- Weak key sizes (AES-128, RSA-1024)
-- Hardcoded keys or passwords
-- Incorrect IV/nonce usage
-- Missing error handling
-
-**Success Criteria**:
-
-- Crypto utility works correctly in browser environment
-- All tests pass for crypto operations
-- No Node.js-specific dependencies
-- Proper error handling and validation
-- Follows existing code patterns in crypto.util.ts
+---
+description: Cryptography and security implementation for WeChat Mini Programs
+mode: skill
+---
+
+**Skill Name**: Cryptography Implementation with WeChat Mini Program Support
+
+**Expertise**: Cryptography, security, WeChat Mini Program compatibility, JavaScript/TypeScript
+
+**Technology Stack**:
+
+- **Primary Libraries**: crypto-js, jsencrypt
+- **Prohibited**: node-forge (not compatible with WeChat Mini Programs)
+- **Hash Algorithms**: MD5, SHA1, SHA256, SHA384, SHA512
+- **Encryption**: AES (CBC, CTR, GCM, ECB modes)
+- **Asymmetric**: RSA with jsencrypt
+
+**Implementation Guidelines**:
+
+1. **Library Selection**:
+
+   - ✅ Use `crypto-js` for symmetric encryption and hashing
+   - ✅ Use `jsencrypt` for RSA operations
+   - ❌ Never use `node-forge` (incompatible with WeChat Mini Programs)
+
+2. **WeChat Mini Program Compatibility**:
+
+   - All cryptography must work in browser environment
+   - No Node.js-specific APIs or dependencies
+   - Test in simulated WeChat Mini Program environment
+
+3. **Best Practices**:
+
+   - Use appropriate key sizes (AES-256, RSA-2048+)
+   - Implement proper IV/nonce generation
+   - Use secure random number generation
+   - Avoid hardcoded keys and secrets
+
+4. **Common Use Cases**:
+   - Password hashing (with salt)
+   - Data encryption at rest
+   - Secure data transmission
+   - Digital signatures
+   - Key generation and management
+
+**Code Patterns for almighty-tool**:
+
+1. **Hash Functions**:
+
+   ```typescript
+   // crypto-js pattern
+   import CryptoJS from 'crypto-js';
+   const hash = CryptoJS.SHA256('data').toString(CryptoJS.enc.Hex);
+   ```
+
+2. **AES Encryption**:
+
+   ```typescript
+   const encrypted = CryptoJS.AES.encrypt(data, key, {
+     iv: iv,
+     mode: CryptoJS.mode.CBC,
+     padding: CryptoJS.pad.Pkcs7,
+   });
+   ```
+
+3. **RSA Operations**:
+   ```typescript
+   import JSEncrypt from 'jsencrypt';
+   const jsEncrypt = new JSEncrypt();
+   jsEncrypt.setPublicKey(publicKey);
+   const encrypted = jsEncrypt.encrypt(data);
+   ```
+
+**Testing Requirements**:
+
+- All crypto operations must be tested with `bun test`
+- Verify compatibility with existing test cases
+- Test edge cases (empty strings, null values, large data)
+- Ensure deterministic output for same inputs
+
+**Security Considerations**:
+
+- Never log sensitive data (keys, passwords, plaintext)
+- Use proper error handling for crypto failures
+- Validate input data before crypto operations
+- Follow cryptographic best practices
+
+**File Locations in Project**:
+
+- Main crypto utility: `src/utils/crypto.util.ts`
+- Test file: `tests/unit/utils/crypto.util.spec.ts`
+- Dependencies: `package.json` (crypto-js, jsencrypt)
+
+**Common Issues to Avoid**:
+
+- Using deprecated algorithms (MD5 for passwords)
+- Weak key sizes (AES-128, RSA-1024)
+- Hardcoded keys or passwords
+- Incorrect IV/nonce usage
+- Missing error handling
+
+**Success Criteria**:
+
+- Crypto utility works correctly in browser environment
+- All tests pass for crypto operations
+- No Node.js-specific dependencies
+- Proper error handling and validation
+- Follows existing code patterns in crypto.util.ts

package/.opencode/skills/typescript-library-dev.md

@@ -1,94 +1,94 @@
----
-description: TypeScript/JavaScript library development with WeChat Mini Program compatibility
-mode: skill
----
-
-**Skill Name**: TypeScript Library Development with WeChat Mini Program Compatibility
-
-**Expertise**: TypeScript, JavaScript, Jest testing, browser compatibility, WeChat Mini Programs
-
-**Key Responsibilities**:
-
-1. Develop and maintain utility libraries in TypeScript
-2. Ensure compatibility with Node.js and browser environments
-3. Maintain WeChat Mini Program compatibility
-4. Write comprehensive unit tests
-5. Follow established code patterns and conventions
-
-**Technology Stack**:
-
-- **Primary Language**: TypeScript (target ES5)
-- **Testing**: Jest with power-assert
-- **Browser Compatibility**: WeChat Mini Program, modern browsers
-- **Cryptography**: crypto-js, jsencrypt (NOT node-forge)
-- **Build Tools**: TypeScript compiler, Prettier, ESLint
-
-**Project Structure Familiarity**:
-
-1. **Source Code**: `src/` directory with common utilities
-
-   - `common/`: Common utilities and constants
-   - `formats/`: Formatting utilities
-   - `i18n/`: Internationalization
-   - `locales/`: Locale data
-   - `utils/`: Utility functions with .util.ts suffix
-
-2. **Testing**: `tests/unit/` matching source structure
-
-   - Tests use `power-assert` for assertions
-   - Follow naming pattern: `*.spec.ts`
-   - Tests should cover all edge cases
-
-3. **Build Output**: `lib/` directory
-   - Generated by TypeScript compilation
-   - Never edit directly
-   - ES5 target for maximum compatibility
-
-**Development Guidelines**:
-
-1. **Code Organization**:
-
-   - Each module exports a single object with methods
-   - Use camelCase for functions/variables, PascalCase for classes/interfaces
-   - Keep files focused and single-purpose
-
-2. **WeChat Mini Program Compatibility**:
-
-   - Avoid Node.js-specific APIs in browser utilities
-   - Use browser-compatible cryptography (crypto-js, jsencrypt)
-   - Test in simulated browser environments
-
-3. **Testing Requirements**:
-
-   - Always run tests with `bun test` or `npm run test`
-   - Ensure 100% test coverage for new features
-   - Follow existing test patterns in each spec file
-   - Use power-assert for readable assertion messages
-
-4. **Quality Assurance**:
-
-   - Run TypeScript compilation with `npm run tsc`
-   - Check for linting issues (despite current ESLint problems)
-   - Use Prettier for code formatting
-   - Verify browser compatibility
-
-5. **Git Workflow**:
-   - Use descriptive commit messages
-   - Pre-commit hooks may require `--no-verify` due to ESLint configuration issues
-   - Keep `lib/` directory out of Git (already ignored)
-
-**Common Pitfalls to Avoid**:
-
-- Using Node.js-specific APIs in browser utilities
-- Forgetting WeChat Mini Program compatibility
-- Breaking existing test cases
-- Not following established code patterns
-- Missing TypeScript type annotations
-
-**Success Criteria**:
-
-- All tests pass (bun test tests/unit/utils/crypto.util.spec.ts)
-- TypeScript compilation succeeds (npm run tsc)
-- Code follows established patterns and conventions
-- WeChat Mini Program compatibility maintained
-- Proper cryptographic libraries used (crypto-js, jsencrypt)
+---
+description: TypeScript/JavaScript library development with WeChat Mini Program compatibility
+mode: skill
+---
+
+**Skill Name**: TypeScript Library Development with WeChat Mini Program Compatibility
+
+**Expertise**: TypeScript, JavaScript, Jest testing, browser compatibility, WeChat Mini Programs
+
+**Key Responsibilities**:
+
+1. Develop and maintain utility libraries in TypeScript
+2. Ensure compatibility with Node.js and browser environments
+3. Maintain WeChat Mini Program compatibility
+4. Write comprehensive unit tests
+5. Follow established code patterns and conventions
+
+**Technology Stack**:
+
+- **Primary Language**: TypeScript (target ES5)
+- **Testing**: Jest with power-assert
+- **Browser Compatibility**: WeChat Mini Program, modern browsers
+- **Cryptography**: crypto-js, jsencrypt (NOT node-forge)
+- **Build Tools**: TypeScript compiler, Prettier, ESLint
+
+**Project Structure Familiarity**:
+
+1. **Source Code**: `src/` directory with common utilities
+
+   - `common/`: Common utilities and constants
+   - `formats/`: Formatting utilities
+   - `i18n/`: Internationalization
+   - `locales/`: Locale data
+   - `utils/`: Utility functions with .util.ts suffix
+
+2. **Testing**: `tests/unit/` matching source structure
+
+   - Tests use `power-assert` for assertions
+   - Follow naming pattern: `*.spec.ts`
+   - Tests should cover all edge cases
+
+3. **Build Output**: `lib/` directory
+   - Generated by TypeScript compilation
+   - Never edit directly
+   - ES5 target for maximum compatibility
+
+**Development Guidelines**:
+
+1. **Code Organization**:
+
+   - Each module exports a single object with methods
+   - Use camelCase for functions/variables, PascalCase for classes/interfaces
+   - Keep files focused and single-purpose
+
+2. **WeChat Mini Program Compatibility**:
+
+   - Avoid Node.js-specific APIs in browser utilities
+   - Use browser-compatible cryptography (crypto-js, jsencrypt)
+   - Test in simulated browser environments
+
+3. **Testing Requirements**:
+
+   - Always run tests with `bun test` or `npm run test`
+   - Ensure 100% test coverage for new features
+   - Follow existing test patterns in each spec file
+   - Use power-assert for readable assertion messages
+
+4. **Quality Assurance**:
+
+   - Run TypeScript compilation with `npm run tsc`
+   - Check for linting issues (despite current ESLint problems)
+   - Use Prettier for code formatting
+   - Verify browser compatibility
+
+5. **Git Workflow**:
+   - Use descriptive commit messages
+   - Pre-commit hooks may require `--no-verify` due to ESLint configuration issues
+   - Keep `lib/` directory out of Git (already ignored)
+
+**Common Pitfalls to Avoid**:
+
+- Using Node.js-specific APIs in browser utilities
+- Forgetting WeChat Mini Program compatibility
+- Breaking existing test cases
+- Not following established code patterns
+- Missing TypeScript type annotations
+
+**Success Criteria**:
+
+- All tests pass (bun test tests/unit/utils/crypto.util.spec.ts)
+- TypeScript compilation succeeds (npm run tsc)
+- Code follows established patterns and conventions
+- WeChat Mini Program compatibility maintained
+- Proper cryptographic libraries used (crypto-js, jsencrypt)

package/.prettierrc.js

@@ -1 +1 @@
-module.exports = require('./templates/prettiers/recommended.js');
+module.exports = require('./templates/prettiers/recommended.js');

package/.yarnrc

@@ -1,12 +1,12 @@
-network-concurrency 1
-registry "https://registry.npmmirror.com"
-canvas_binary_host_mirror "https://npmmirror.com/mirrors/canvas"
-sass_binary_site "https://npmmirror.com/mirrors/node-sass"
-phantomjs_cdnurl "https://npmmirror.com/mirrors/phantomjs"
-electron_mirror "https://npmmirror.com/mirrors/electron"
-sqlite3_binary_host_mirror "http://npmmirror.com/mirrors/sqlite3"
-profiler_binary_host_mirror "http://npmmirror.com/mirrors/node-inspector"
-chromedriver_cdnurl "https://npmmirror.com/mirrors/chromedriver"
-operadriver_cdnurl "https://npmmirror.com/mirrors/operadriver"
-sentrycli_cdnurl "https://npmmirror.com/mirrors/sentry-cli"
+network-concurrency 1
+registry "https://registry.npmmirror.com"
+canvas_binary_host_mirror "https://npmmirror.com/mirrors/canvas"
+sass_binary_site "https://npmmirror.com/mirrors/node-sass"
+phantomjs_cdnurl "https://npmmirror.com/mirrors/phantomjs"
+electron_mirror "https://npmmirror.com/mirrors/electron"
+sqlite3_binary_host_mirror "http://npmmirror.com/mirrors/sqlite3"
+profiler_binary_host_mirror "http://npmmirror.com/mirrors/node-inspector"
+chromedriver_cdnurl "https://npmmirror.com/mirrors/chromedriver"
+operadriver_cdnurl "https://npmmirror.com/mirrors/operadriver"
+sentrycli_cdnurl "https://npmmirror.com/mirrors/sentry-cli"
 fse_binary_host_mirror "https://npmmirror.com/mirrors/fsevents"

package/AGENTS.md

@@ -1,69 +1,69 @@
-# OpenCode Agents
-
-This document helps OpenCode understand the project structure and coding patterns used in the almighty-tool project.
-
-## Project Overview
-
-- **Type**: JavaScript/TypeScript tool library
-- **Build Tool**: TypeScript, Jest for testing
-- **Target Environment**: Node.js and browser environments (ES5 target)
-
-## Directory Structure
-
-```
-almighty-tool/
-├── src/                 # Source code
-│   ├── common/         # Common utilities and constants
-│   ├── formats/        # Formatting utilities
-│   ├── i18n/           # Internationalization
-│   ├── locales/        # Locale data
-│   ├── utils/          # Utility functions
-│   │   ├── basic.util.ts      # Basic utilities
-│   │   ├── color.util.ts      # Color manipulation
-│   │   ├── crypto.util.ts     # Cryptography utilities
-│   │   ├── date.util.ts       # Date and time utilities
-│   │   └── ... (other utilities)
-├── tests/               # Test files
-│   └── unit/           # Unit tests matching src structure
-├── lib/                 # Compiled output (ignored by Git)
-└── types/              # TypeScript type definitions
-```
-
-## Development Tools
-
-- **Testing**: Jest with power-assert
-- **Linting**: ESLint with custom rules from templates/eslints/recommended.js
-- **Formatting**: Prettier
-- **Type Checking**: TypeScript
-
-## Code Conventions
-
-1. **Naming**: camelCase for functions/variables, PascalCase for classes/interfaces
-2. **File Structure**: Each utility module exports a single object with methods
-3. **Testing**: Tests use `power-assert` module
-4. **Imports**: Relative imports, TypeScript ES modules
-
-## Build Commands
-
-- `npm run test` or `bun test` - Run all tests
-- `npm run tsc` - TypeScript compilation
-- `npm run lint` - ESLint checking (currently has config issues)
-- `npm run check` - Run tests and lint
-
-## Project-Specific Guidelines
-
-- Keep compatibility with WeChat Mini Programs for browser-facing utilities
-- Use crypto-js and jsencrypt for cryptography (not node-forge)
-- Test all changes with the existing test suite
-- Follow the existing code patterns in each module
-
-## Git Workflow
-
-- Pre-commit hooks configured via yorkie (gitHooks in package.json)
-- Commit messages should be descriptive and follow conventional commits
-
-## Notes
-
-- `lib/` directory contains compiled output, should not be manually edited
-- ESLint configuration has issues with jest plugin (need to fix dependencies)
-- Use `git commit --no-verify` temporarily to bypass pre-commit hooks due to ESLint issues
+# OpenCode Agents
+
+This document helps OpenCode understand the project structure and coding patterns used in the almighty-tool project.
+
+## Project Overview
+
+- **Type**: JavaScript/TypeScript tool library
+- **Build Tool**: TypeScript, Jest for testing
+- **Target Environment**: Node.js and browser environments (ES5 target)
+
+## Directory Structure
+
+```
+almighty-tool/
+├── src/                 # Source code
+│   ├── common/         # Common utilities and constants
+│   ├── formats/        # Formatting utilities
+│   ├── i18n/           # Internationalization
+│   ├── locales/        # Locale data
+│   ├── utils/          # Utility functions
+│   │   ├── basic.util.ts      # Basic utilities
+│   │   ├── color.util.ts      # Color manipulation
+│   │   ├── crypto.util.ts     # Cryptography utilities
+│   │   ├── date.util.ts       # Date and time utilities
+│   │   └── ... (other utilities)
+├── tests/               # Test files
+│   └── unit/           # Unit tests matching src structure
+├── lib/                 # Compiled output (ignored by Git)
+└── types/              # TypeScript type definitions
+```
+
+## Development Tools
+
+- **Testing**: Jest with power-assert
+- **Linting**: ESLint with custom rules from templates/eslints/recommended.js
+- **Formatting**: Prettier
+- **Type Checking**: TypeScript
+
+## Code Conventions
+
+1. **Naming**: camelCase for functions/variables, PascalCase for classes/interfaces
+2. **File Structure**: Each utility module exports a single object with methods
+3. **Testing**: Tests use `power-assert` module
+4. **Imports**: Relative imports, TypeScript ES modules
+
+## Build Commands
+
+- `npm run test` or `bun test` - Run all tests
+- `npm run tsc` - TypeScript compilation
+- `npm run lint` - ESLint checking (currently has config issues)
+- `npm run check` - Run tests and lint
+
+## Project-Specific Guidelines
+
+- Keep compatibility with WeChat Mini Programs for browser-facing utilities
+- Use crypto-js and jsencrypt for cryptography (not node-forge)
+- Test all changes with the existing test suite
+- Follow the existing code patterns in each module
+
+## Git Workflow
+
+- Pre-commit hooks configured via yorkie (gitHooks in package.json)
+- Commit messages should be descriptive and follow conventional commits
+
+## Notes
+
+- `lib/` directory contains compiled output, should not be manually edited
+- ESLint configuration has issues with jest plugin (need to fix dependencies)
+- Use `git commit --no-verify` temporarily to bypass pre-commit hooks due to ESLint issues

package/CHANGELOG.md

@@ -1,7 +1,7 @@
-# CHNAGE LOG
-
-## Develop
-
-### 2020-09-21 10:40
-
-- 增加request options的name参数, 已经result增加name参数
+# CHNAGE LOG
+
+## Develop
+
+### 2020-09-21 10:40
+
+- 增加request options的name参数, 已经result增加name参数

package/README.md

@@ -1,11 +1,11 @@
-# almighty-tool
-
-> almighty common lib
-
-## Build Setup
-
-``` bash
-$ bun install
-$ bun run test
-$ bun run test --watch
-```
+# almighty-tool
+
+> almighty common lib
+
+## Build Setup
+
+``` bash
+$ bun install
+$ bun run test
+$ bun run test --watch
+```