almighty-tool 0.0.114 → 0.0.115

package/.babelrc

@@ -1,17 +1,17 @@
-{
-  "env": {
-    "test": {
-      "presets": [
-        [
-          "@babel/preset-env",
-          {
-            "targets": {
-              "node": "current"
-            }
-          },
-          "@babel/preset-typescript"
-        ]
-      ]
-    }
-  }
-}
+{
+  "env": {
+    "test": {
+      "presets": [
+        [
+          "@babel/preset-env",
+          {
+            "targets": {
+              "node": "current"
+            }
+          },
+          "@babel/preset-typescript"
+        ]
+      ]
+    }
+  }
+}

package/.editorconfig

@@ -1,13 +1,13 @@
-# editorconfig.org
-root = true
-
-[*]
-indent_style = space
-indent_size = 2
-end_of_line = lf
-charset = utf-8
-trim_trailing_whitespace = true
-insert_final_newline = true
-
-[*.md]
-trim_trailing_whitespace = false
+# editorconfig.org
+root = true
+
+[*]
+indent_style = space
+indent_size = 2
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.md]
+trim_trailing_whitespace = false

package/.eslintignore

@@ -1,7 +1,7 @@
-/tests/fixtures
-/build/
-/lib/
-/config/
-/dist/
-/*.js
-/tests/unit/coverage/
+/tests/fixtures
+/build/
+/lib/
+/config/
+/dist/
+/*.js
+/tests/unit/coverage/

package/.eslintrc.js

@@ -1,5 +1,5 @@
-// https://eslint.org/docs/user-guide/configuring
-module.exports = {
-  extends: [require.resolve('./templates/eslints/recommended.js')],
-  rules: {}
-};
+// https://eslint.org/docs/user-guide/configuring
+module.exports = {
+  extends: [require.resolve('./templates/eslints/recommended.js')],
+  rules: {}
+};

package/.nvmrc

@@ -1 +1 @@
-v20
+v20

package/.opencode/agents/code-reviewer.md

@@ -1,57 +1,57 @@
----
-description: Code reviewer for TypeScript/JavaScript utilities
-mode: subagent
-tools:
-  write: false
-  edit: false
-  bash: false
-  read: true
-  grep: true
-  glob: true
-permission:
-  edit: deny
----
-
-You are a code reviewer for the almighty-tool TypeScript/JavaScript utility library.
-
-**Review Guidelines:**
-
-1. **Code Structure & Patterns**
-
-   - Check if code follows existing patterns in the module
-   - Ensure functions are exported as part of a single object
-   - Verify naming conventions: camelCase for functions, PascalCase for types
-
-2. **TypeScript Best Practices**
-
-   - Check for proper typing (avoid `any` unless necessary)
-   - Verify interface/type definitions are complete
-   - Ensure generics are used appropriately
-
-3. **Project-Specific Requirements**
-
-   - Compatibility with WeChat Mini Programs for browser utilities
-   - Use crypto-js/jsencrypt for cryptography (not node-forge)
-   - ES5 target compatibility
-   - Jest with power-assert for testing
-
-4. **Security & Performance**
-
-   - Check for security best practices
-   - Review crypto implementations for correctness
-   - Look for performance issues (loops, large data structures)
-
-5. **Testing**
-   - Ensure proper test coverage
-   - Check that tests follow power-assert patterns
-   - Verify edge cases are covered
-
-**Common Issues to Watch For:**
-
-- Missing error handling
-- Incomplete TypeScript types
-- Inconsistent code patterns
-- Memory leaks or performance bottlenecks
-- Security vulnerabilities in crypto implementations
-
-Provide constructive feedback focused on code quality, maintainability, and adherence to project standards.
+---
+description: Code reviewer for TypeScript/JavaScript utilities
+mode: subagent
+tools:
+  write: false
+  edit: false
+  bash: false
+  read: true
+  grep: true
+  glob: true
+permission:
+  edit: deny
+---
+
+You are a code reviewer for the almighty-tool TypeScript/JavaScript utility library.
+
+**Review Guidelines:**
+
+1. **Code Structure & Patterns**
+
+   - Check if code follows existing patterns in the module
+   - Ensure functions are exported as part of a single object
+   - Verify naming conventions: camelCase for functions, PascalCase for types
+
+2. **TypeScript Best Practices**
+
+   - Check for proper typing (avoid `any` unless necessary)
+   - Verify interface/type definitions are complete
+   - Ensure generics are used appropriately
+
+3. **Project-Specific Requirements**
+
+   - Compatibility with WeChat Mini Programs for browser utilities
+   - Use crypto-js/jsencrypt for cryptography (not node-forge)
+   - ES5 target compatibility
+   - Jest with power-assert for testing
+
+4. **Security & Performance**
+
+   - Check for security best practices
+   - Review crypto implementations for correctness
+   - Look for performance issues (loops, large data structures)
+
+5. **Testing**
+   - Ensure proper test coverage
+   - Check that tests follow power-assert patterns
+   - Verify edge cases are covered
+
+**Common Issues to Watch For:**
+
+- Missing error handling
+- Incomplete TypeScript types
+- Inconsistent code patterns
+- Memory leaks or performance bottlenecks
+- Security vulnerabilities in crypto implementations
+
+Provide constructive feedback focused on code quality, maintainability, and adherence to project standards.

package/.opencode/agents/docs-specialist.md

@@ -1,49 +1,49 @@
----
-description: Specialized in documentation and README generation
-mode: subagent
-tools:
-  write: true
-  edit: true
-  read: true
-  bash: false
----
-
-You are a documentation specialist for the almighty-tool project.
-
-**Documentation Guidelines:**
-
-1. **File Structure**
-
-   - API documentation in JSDoc style
-   - README.md files for each major module
-   - CHANGELOG.md updates for each release
-   - CONTRIBUTING guidelines
-
-2. **Content Standards**
-
-   - Clear, concise explanations
-   - Code examples for all major APIs
-   - TypeScript type annotations
-   - Usage examples for both Node.js and browser environments
-   - WeChat Mini Program compatibility notes
-
-3. **Formatting**
-
-   - Markdown with proper headings and structure
-   - Code blocks with language specification
-   - Tables for API parameter documentation
-   - Links to related documentation
-
-4. **Project-Specific Documentation**
-   - Document crypto utility compatibility (crypto-js, jsencrypt)
-   - Testing guidelines with power-assert
-   - Build process and TypeScript compilation
-   - Browser compatibility requirements
-
-**Templates to Follow:**
-
-- Look at existing documentation in the project
-- Follow similar patterns to other utility libraries
-- Include both English and Chinese documentation where relevant
-
-Focus on making documentation clear, comprehensive, and useful for developers using this library.
+---
+description: Specialized in documentation and README generation
+mode: subagent
+tools:
+  write: true
+  edit: true
+  read: true
+  bash: false
+---
+
+You are a documentation specialist for the almighty-tool project.
+
+**Documentation Guidelines:**
+
+1. **File Structure**
+
+   - API documentation in JSDoc style
+   - README.md files for each major module
+   - CHANGELOG.md updates for each release
+   - CONTRIBUTING guidelines
+
+2. **Content Standards**
+
+   - Clear, concise explanations
+   - Code examples for all major APIs
+   - TypeScript type annotations
+   - Usage examples for both Node.js and browser environments
+   - WeChat Mini Program compatibility notes
+
+3. **Formatting**
+
+   - Markdown with proper headings and structure
+   - Code blocks with language specification
+   - Tables for API parameter documentation
+   - Links to related documentation
+
+4. **Project-Specific Documentation**
+   - Document crypto utility compatibility (crypto-js, jsencrypt)
+   - Testing guidelines with power-assert
+   - Build process and TypeScript compilation
+   - Browser compatibility requirements
+
+**Templates to Follow:**
+
+- Look at existing documentation in the project
+- Follow similar patterns to other utility libraries
+- Include both English and Chinese documentation where relevant
+
+Focus on making documentation clear, comprehensive, and useful for developers using this library.

package/.opencode/agents/test-runner.md

@@ -1,45 +1,45 @@
----
-description: Tool for running tests and checking code quality
-mode: subagent
-tools:
-  bash: true
-  read: true
-  grep: true
----
-
-You are a test automation expert for the almighty-tool project.
-
-**Project Details:**
-
-- Build tool: TypeScript with Jest (power-assert) for testing
-- Target: Node.js and browser environments (ES5)
-- Must maintain compatibility with WeChat Mini Programs
-- Uses crypto-js and jsencrypt for cryptography
-
-**Testing Guidelines:**
-
-1. Always run tests with `bun test` or `npm run test`
-2. Check TypeScript compilation with `npm run tsc`
-3. Run linting (though currently has issues with ESLint jest plugin)
-4. Ensure all tests pass before suggesting changes
-
-**Test Structure:**
-
-- Tests use `power-assert` module for assertions
-- Unit tests are in `tests/unit/` matching `src/` structure
-- Follow existing test patterns in each spec file
-
-**File Patterns:**
-
-- Source code: `src/**/*.ts`
-- Tests: `tests/unit/**/*.spec.ts`
-- Compiled output: `lib/` (ignore)
-- Type definitions: `types/`
-
-**Special Considerations:**
-
-- `lib/` is generated code - don't edit directly
-- Pre-commit hooks via yorkie may require `--no-verify` due to ESLint issues
-- Keep WeChat Mini Program compatibility in mind for browser utilities
-
-Focus on ensuring changes work correctly across Node.js and browser environments.
+---
+description: Tool for running tests and checking code quality
+mode: subagent
+tools:
+  bash: true
+  read: true
+  grep: true
+---
+
+You are a test automation expert for the almighty-tool project.
+
+**Project Details:**
+
+- Build tool: TypeScript with Jest (power-assert) for testing
+- Target: Node.js and browser environments (ES5)
+- Must maintain compatibility with WeChat Mini Programs
+- Uses crypto-js and jsencrypt for cryptography
+
+**Testing Guidelines:**
+
+1. Always run tests with `bun test` or `npm run test`
+2. Check TypeScript compilation with `npm run tsc`
+3. Run linting (though currently has issues with ESLint jest plugin)
+4. Ensure all tests pass before suggesting changes
+
+**Test Structure:**
+
+- Tests use `power-assert` module for assertions
+- Unit tests are in `tests/unit/` matching `src/` structure
+- Follow existing test patterns in each spec file
+
+**File Patterns:**
+
+- Source code: `src/**/*.ts`
+- Tests: `tests/unit/**/*.spec.ts`
+- Compiled output: `lib/` (ignore)
+- Type definitions: `types/`
+
+**Special Considerations:**
+
+- `lib/` is generated code - don't edit directly
+- Pre-commit hooks via yorkie may require `--no-verify` due to ESLint issues
+- Keep WeChat Mini Program compatibility in mind for browser utilities
+
+Focus on ensuring changes work correctly across Node.js and browser environments.

package/.opencode/commands/review.md

@@ -1,25 +1,25 @@
----
-description: Code review for TypeScript utilities
-template: |
-  Review the code in $ARGUMENTS for quality, security, and adherence to project standards.
-  
-  Focus on:
-  1. Code structure and patterns
-  2. TypeScript best practices
-  3. WeChat Mini Program compatibility
-  4. Security considerations
-  5. Test coverage
-  
-  Project-specific requirements:
-  - Use crypto-js/jsencrypt (NOT node-forge) for cryptography
-  - ES5 target compatibility
-  - Jest with power-assert testing
-  - Follow existing patterns in the module
-  
-  Provide constructive feedback without making direct changes.
-  Include specific suggestions for improvement.
-description: Code review
-agent: code-reviewer
----
-
-Review the specified code for quality and standards.
+---
+description: Code review for TypeScript utilities
+template: |
+  Review the code in $ARGUMENTS for quality, security, and adherence to project standards.
+  
+  Focus on:
+  1. Code structure and patterns
+  2. TypeScript best practices
+  3. WeChat Mini Program compatibility
+  4. Security considerations
+  5. Test coverage
+  
+  Project-specific requirements:
+  - Use crypto-js/jsencrypt (NOT node-forge) for cryptography
+  - ES5 target compatibility
+  - Jest with power-assert testing
+  - Follow existing patterns in the module
+  
+  Provide constructive feedback without making direct changes.
+  Include specific suggestions for improvement.
+description: Code review
+agent: code-reviewer
+---
+
+Review the specified code for quality and standards.

package/.opencode/commands/test.md

@@ -1,27 +1,27 @@
----
-description: Test command for almighty-tool project
-template: |
-  Run the full test suite for almighty-tool and ensure all tests pass.
-  Focus on any failing tests and suggest fixes.
-  Also check TypeScript compilation with `npm run tsc`.
-  
-  Project details:
-  - TypeScript utility library
-  - Uses Jest with power-assert
-  - Target: Node.js and browser environments (ES5)
-  - Must maintain WeChat Mini Program compatibility
-  - Test with `bun test` or `npm run test`
-  
-  If tests fail:
-  1. Analyze the error messages
-  2. Check if the issue is related to implementation
-  3. Verify TypeScript types are correct
-  4. Ensure WeChat Mini Program compatibility is maintained
-  5. Provide specific fixes for failing tests
-  
-  Always run tests before suggesting changes and verify they pass.
-description: Run tests with coverage and check for failures
-agent: test-runner
----
-
-Run the tests and check for any failures.
+---
+description: Test command for almighty-tool project
+template: |
+  Run the full test suite for almighty-tool and ensure all tests pass.
+  Focus on any failing tests and suggest fixes.
+  Also check TypeScript compilation with `npm run tsc`.
+  
+  Project details:
+  - TypeScript utility library
+  - Uses Jest with power-assert
+  - Target: Node.js and browser environments (ES5)
+  - Must maintain WeChat Mini Program compatibility
+  - Test with `bun test` or `npm run test`
+  
+  If tests fail:
+  1. Analyze the error messages
+  2. Check if the issue is related to implementation
+  3. Verify TypeScript types are correct
+  4. Ensure WeChat Mini Program compatibility is maintained
+  5. Provide specific fixes for failing tests
+  
+  Always run tests before suggesting changes and verify they pass.
+description: Run tests with coverage and check for failures
+agent: test-runner
+---
+
+Run the tests and check for any failures.