genlayer 0.18.2 → 0.18.4

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.18.4 (2025-06-27)
+
+### Bug Fixes
+
+* refactor log output formatting and address spinner display ([#228](https://github.com/yeagerai/genlayer-cli/issues/228)) ([ea0ac10](https://github.com/yeagerai/genlayer-cli/commit/ea0ac100cdbed0cf184ae1eaf1d9c0fd580fc92c))
+
+## 0.18.3 (2025-05-29)
+
 ## 0.18.2 (2025-05-29)
 
 ## 0.18.2-beta.0 (2025-05-29)

package/CONTRIBUTING.md

@@ -0,0 +1,117 @@
+# Contributing to GenLayer CLI
+
+We're thrilled that you're interested in contributing to the GenLayer CLI! This document will guide you through the contribution process.
+
+## What is the GenLayer CLI?
+
+The GenLayer CLI is a command-line tool designed to:
+1. Streamline the setup and local execution of the GenLayer simulator. It automates the process of downloading and launching the GenLayer simulator, making it easy to start simulating and testing locally with minimal setup.
+2. Deploy Intelligent Contracts on any network, read their state and send transactions to them.
+3. Perform Validators operations
+
+## How You Can Contribute?
+
+Contributions to the GenLayer CLI are welcome in several forms:
+
+### Testing the CLI and Providing Feedback
+
+Help us make the CLI better by testing and giving feedback:
+
+- Start by installing the CLI globally using the command:
+  ```sh
+  $ npm install -g genlayer
+  ```
+- Try out the CLI features and tell us what you think through our [feedback form](https://forms.gle/ZbbxHsZrJxKucurB7) or on our [Discord Channel](https://discord.gg/8Jm4v89VAu).
+- If you find any issues, please report them on our [GitHub issues page](https://github.com/yeagerai/genlayer-cli/issues).
+
+### Sharing New Ideas and Use Cases
+
+Have ideas for new features or use cases? We're eager to hear them! But first:
+
+- Ensure you have the CLI installed to explore existing functionality.
+- After familiarizing yourself with the CLI, contribute your unique use case and share your ideas in our [Discord channel](https://discord.gg/8Jm4v89VAu).
+
+### Bug fixing and Feature development
+
+#### 1. Set yourself up to start coding
+
+- **1.1. Pick an issue**: Select one from the project GitHub repository [issue list](https://github.com/yeagerai/genlayer-cli/issues) and assign it to yourself.
+
+- **1.2. Create a branch**: create the branch that you will work on by using the link provided in the issue details page (right panel at the bottom - section "Development")
+
+- **1.3. Setup the CLI locally**: clone the repository and install dependencies
+
+   ```sh
+   $ git clone https://github.com/yeagerai/genlayer-cli.git
+   $ cd genlayer-cli
+   $ npm install
+   ```
+
+- **1.4. Run the CLI in dev mode**: to run the CLI in development mode with hot reload enabled:
+
+   ```sh
+   $ npm run dev
+   ```
+
+- **1.5. Test the CLI locally**: to test the CLI commands locally during development:
+
+   ```sh
+   $ node dist/index.js <command>
+   ```
+
+   For example:
+   ```sh
+   $ node dist/index.js init
+   $ node dist/index.js up
+   $ node dist/index.js validators get
+   ```
+
+- **1.6. Run unit tests**:
+The GenLayer CLI uses Jest in combination with ts-jest to handle testing of TypeScript files. The configuration is tailored to support ES Modules (ESM), aligning with the latest JavaScript standards and ensuring compatibility with modern tooling and Node.js features.
+
+##### Running Tests
+
+To run the tests, use the following command:
+
+```bash
+npm run test
+```
+
+This command sets the appropriate Node.js options to handle ES Modules and watches for changes in the test files, making it suitable for development.
+
+##### Test Configuration
+
+Our `jest.config.js` is set up as follows:
+
+- ES Module Support: Configured to treat .ts files as ES Modules.
+- Test Environment: Uses Node.js as the testing environment.
+- Transformation: Utilizes ts-jest with an ESM preset to process TypeScript files.
+
+Tests are located in the tests/ directory and should be named using the following pattern: [filename].test.ts. When writing tests, you can use all Jest functionalities such as describe, test, expect, and Jest mocks for testing asynchronous functions, component interactions, or API calls.
+
+#### 2. Submit your solution
+
+- **2.1. Prettier Formatter on Save File**: Configure IDE extensions to format your code with [Prettier](https://prettier.io/) before submitting it.
+- **2.2. Code solution**: implement the solution in the code.
+- **2.3. Run tests**: Ensure all tests pass before submitting:
+   ```sh
+   $ npm run test
+   ```
+- **2.4. Pull Request**: Submit your changes through a pull request (PR). Fill the entire PR template and set the PR title as a valid conventional commit.
+- **2.5. Check PR and issue linking**: if the issue and the PR are not linked, you can do it manually in the right panel of the Pull Request details page.  
+- **2.6. Peer Review**: One or more core contributors will review your PR. They may suggest changes or improvements.
+- **2.7. Approval and Merge**: After approval from the reviewers, you can merge your PR with a squash and merge type of action.
+
+
+### Improving Documentation
+
+To contribute to our docs, visit our [Documentation Repository](https://github.com/yeagerai/genlayer-docs) to create new issues or contribute to existing issues.
+
+## Community
+
+Connect with the GenLayer community to discuss, collaborate, and share insights:
+
+- **[Discord Channel](https://discord.gg/8Jm4v89VAu)**: Our primary hub for discussions, support, and announcements.
+- **[Telegram Group](https://t.me/genlayer)**: For more informal chats and quick updates.
+
+Your continuous feedback drives better product development. Please engage with us regularly to test, discuss, and improve the GenLayer CLI.

package/README.md

@@ -14,77 +14,275 @@ npm install -g genlayer
 
 ## Usage
 
-To initialize and start the GenLayer simulator, run the following command:
+Each command includes syntax, usage information, and examples to help you effectively use the CLI for interacting with the GenLayer environment.
+
+### Command line syntax
+
+General syntax for using the GenLayer CLI:
 
 ```bash
-genlayer init
+genlayer command [command options] [arguments...]
 ```
 
-This command will download the necessary components and start the simulator. Once initialized, you will be ready to execute further commands (to be implemented) to interact with the simulator.
+### Commands and usage
 
-## Contributing
+#### Initialize
 
-Contributions to the GenLayer CLI are welcome! Please feel free to fork the repository, make your changes, and submit a pull request. We appreciate your efforts to improve the software.
+Prepares and verifies your environment to run the GenLayer Studio.
 
-### Running the CLI from the repository
+```bash
+USAGE:
+   genlayer init [options]
+
+OPTIONS:
+   --numValidators <numValidators>       Number of validators (default: "5")
+   --headless                            Headless mode (default: false)
+   --reset-db                            Reset Database (default: false)
+   --localnet-version <localnetVersion>  Select a specific localnet version
+   --ollama                              Enable Ollama container (default: false)
+
+EXAMPLES:
+   genlayer init
+   genlayer init --numValidators 10 --headless --reset-db --localnet-version v0.10.2
+   genlayer init --ollama
+```
 
-First, install the dependencies and start the build process
+##### Version Compatibility
+
+The GenLayer CLI always uses the latest compatible version of the environment, ensuring that you benefit from the most recent features, bug fixes, and optimizations without requiring manual updates. If a specific version is needed, you can specify it using the --localnet-version option when initializing the environment.
 
 ```bash
-npm install
-npm run dev
+genlayer init --localnet-version v0.10.2
 ```
 
-This will continuously rebuild the CLI from the source
+#### Start GenLayer environment
 
-Then in another window execute the CLI commands like so:
+Launches the GenLayer environment and the Studio, initializing a fresh set of database and accounts.
 
 ```bash
-node dist/index.js init
+USAGE:
+   genlayer up [options]
+
+OPTIONS:
+   --reset-validators               Remove all current validators and create new random ones (default: false)
+   --numValidators <numValidators>  Number of validators (default: "5")
+   --headless                       Headless mode (default: false)
+   --reset-db                       Reset Database (default: false)
+   --ollama                         Enable Ollama container (default: false)
+
+EXAMPLES:
+   genlayer up
+   genlayer up --reset-validators --numValidators 8 --headless --reset-db
+   genlayer up --ollama
+```
+
+#### Stop GenLayer environment
+
+Stops all running GenLayer Localnet services.
+
+```bash
+USAGE:
+   genlayer stop
 ```
 
-## Testing
+#### Create a New GenLayer Project
+
+Initialize a new GenLayer project using a local template.
 
-### Overview
+```bash
+USAGE:
+   genlayer new <projectName> [options]
 
-The GenLayer CLI uses Jest in combination with ts-jest to handle testing of TypeScript files. The configuration is tailored to support ES Modules (ESM), aligning with the latest JavaScript standards and ensuring compatibility with modern tooling and Node.js features.
+OPTIONS:
+   --path <directory>  Specify the directory for the new project (default: ".")
+   --overwrite         Overwrite existing directory if it exists (default: false)
+
+EXAMPLES:
+   genlayer new myProject
+   genlayer new myProject --path ./customDir
+   genlayer new myProject --overwrite
+```
 
-### Running Tests
+#### Manage CLI Configuration
 
-To run the tests, use the following command:
+Configure the GenLayer CLI settings.
 
 ```bash
-npm run test
+USAGE:
+   genlayer config <command> [options]
+
+COMMANDS:
+   set <key=value>  Set a configuration value
+   get [key]        Get the current configuration
+   reset <key>      Reset a configuration value to its default
+
+EXAMPLES:
+   genlayer config get
+   genlayer config get defaultOllamaModel
+   genlayer config set defaultOllamaModel=deepseek-r1
+   genlayer config reset keyPairPath
 ```
 
-This command sets the appropriate Node.js options to handle ES Modules and watches for changes in the test files, making it suitable for development.
+#### Network Management
 
-### Test Configuration
+Set the network to use for contract operations.
 
-Our `jest.config.js` is set up as follows:
+```bash
+USAGE:
+   genlayer network [network]
 
-- ES Module Support: Configured to treat .ts files as ES Modules.
-- Test Environment: Uses Node.js as the testing environment.
-- Transformation: Utilizes ts-jest with an ESM preset to process TypeScript files.
+EXAMPLES:
+   genlayer network
+   genlayer network testnet
+   genlayer network mainnet
+```
 
-Tests are located in the tests/ directory and should be named using the following pattern: [filename].test.ts. When writing tests, you can use all Jest functionalities such as describe, test, expect, and Jest mocks for testing asynchronous functions, component interactions, or API calls.
+#### Deploy and Call Intelligent Contracts
 
-## License
+Deploy and interact with intelligent contracts.
 
-This project is licensed under the ... License - see the [LICENSE](LICENSE) file for details.
+```bash
+USAGE:
+   genlayer deploy [options]
+   genlayer call <contractAddress> <method> [options]
+   genlayer write <contractAddress> <method> [options]
+
+OPTIONS (deploy):
+   --contract <contractPath>  (Optional) Path to the intelligent contract to deploy
+   --rpc <rpcUrl>             RPC URL for the network
+   --args <args...>           Positional arguments for the contract (space-separated, use quotes for multi-word arguments)
+
+OPTIONS (call):
+   --rpc <rpcUrl>             RPC URL for the network
+   --args <args...>           Positional arguments for the method (space-separated, use quotes for multi-word arguments)
+
+OPTIONS (write):
+   --rpc <rpcUrl>             RPC URL for the network
+   --args <args...>           Positional arguments for the method (space-separated, use quotes for multi-word arguments)
+
+EXAMPLES:
+   genlayer deploy
+   genlayer deploy --contract ./my_contract.gpy
+   genlayer deploy --contract ./my_contract.gpy --args "arg1" "arg2" 123
+   genlayer call 0x123456789abcdef greet --args "Hello World!"
+   genlayer write 0x123456789abcdef updateValue --args 42
+```
+
+##### Deploy Behavior
+- If `--contract` is specified, the command will **deploy the given contract**.
+- If `--contract` is omitted, the CLI will **search for scripts inside the `deploy` folder**, sort them, and execute them sequentially.
+
+##### Call vs Write
+- `call` - Calls a contract method without sending a transaction or changing the state (read-only)
+- `write` - Sends a transaction to a contract method that modifies the state
+
+#### Keypair Management
+
+Generate and manage keypairs.
+
+```bash
+USAGE:
+   genlayer keygen create [options]
 
-## Credits
+OPTIONS:
+   --output <path>    Path to save the keypair (default: "./keypair.json")
+   --overwrite        Overwrite the existing file if it already exists (default: false)
 
-- TBD
+EXAMPLES:
+   genlayer keygen create
+   genlayer keygen create --output ./my_key.json --overwrite
+```
+
+#### Update Resources
+
+Manage and update models or configurations.
+
+```bash
+USAGE:
+   genlayer update ollama [options]
+
+OPTIONS:
+   --model [model-name]  Specify the model to update or pull
+   --remove              Remove the specified model instead of updating
+
+EXAMPLES:
+   genlayer update ollama
+   genlayer update ollama --model deepseek-r1
+   genlayer update ollama --model deepseek-r1 --remove
+```
+
+#### Validator Management
+
+Manage validator operations.
+
+```bash
+USAGE:
+   genlayer validators <command> [options]
+
+COMMANDS:
+   get [--address <validatorAddress>]     Retrieve details of a specific validator or all validators
+   delete [--address <validatorAddress>]  Delete a specific validator or all validators
+   count                                  Count all validators
+   update <validatorAddress> [options]    Update a validator details
+   create-random [options]                Create random validators
+   create [options]                       Create a new validator
+
+OPTIONS (update):
+   --stake <stake>                        New stake for the validator
+   --provider <provider>                  New provider for the validator
+   --model <model>                        New model for the validator
+   --config <config>                      New JSON config for the validator
+
+OPTIONS (create-random):
+   --count <count>                        Number of validators to create (default: "1")
+   --providers <providers...>             Space-separated list of provider names (e.g., openai ollama)
+   --models <models...>                   Space-separated list of model names (e.g., gpt-4 gpt-4o)
+
+OPTIONS (create):
+   --stake <stake>                        Stake amount for the validator (default: "1")
+   --config <config>                      Optional JSON configuration for the validator
+   --provider <provider>                  Specify the provider for the validator
+   --model <model>                        Specify the model for the validator
+
+EXAMPLES:
+   genlayer validators get
+   genlayer validators get --address 0x123456789abcdef
+
+   genlayer validators count
+   genlayer validators delete --address 0x123456789abcdef
+   genlayer validators update 0x123456789abcdef --stake 100 --provider openai --model gpt-4
+
+   genlayer validators create
+   genlayer validators create --stake 50 --provider openai --model gpt-4
+   genlayer validators create-random --count 3 --providers openai --models gpt-4 gpt-4o
+```
+
+### Running the CLI from the repository
+
+First, install the dependencies and start the build process
 
-## Contact
+```bash
+npm install
+npm run dev
+```
 
-- TBD
+This will continuously rebuild the CLI from the source
 
-## Further Development
+Then in another window execute the CLI commands like so:
 
-Further commands are planned for implementation to enhance interaction with the GenLayer simulator. Stay tuned for updates.
+```bash
+node dist/index.js init
+```
 
-## Feedback
+## Documentation
+
+For detailed information on how to use GenLayer CLI, please refer to our [documentation](https://docs.genlayer.com/).
+
+## Contributing
+
+We welcome contributions to GenLayerJS SDK! Whether it's new features, improved infrastructure, or better documentation, your input is valuable. Please read our [CONTRIBUTING](https://github.com/yeagerai/genlayer-js/blob/main/CONTRIBUTING.md) guide for guidelines on how to submit your contributions.
+
+## License
+
+This project is licensed under the ... License - see the [LICENSE](LICENSE) file for details.
 
-If you have any feedback, please reach out to us at the contact provided above.

package/dist/index.js

@@ -17723,7 +17723,7 @@ var require_semver2 = __commonJS({
 import { program } from "commander";
 
 // package.json
-var version = "0.18.2";
+var version = "0.18.4";
 var package_default = {
   name: "genlayer",
   version,
@@ -20658,6 +20658,7 @@ function ora(options) {
 
 // src/lib/actions/BaseAction.ts
 import inquirer from "inquirer";
+import { inspect } from "util";
 
 // src/lib/accounts/KeypairManager.ts
 import { writeFileSync, existsSync, readFileSync } from "fs";
@@ -40979,18 +40980,10 @@ var BaseAction = class extends ConfigFileManager {
     }
   }
   formatOutput(data) {
-    if (data instanceof Error) {
-      const errorDetails = {
-        name: data.name,
-        message: data.message,
-        ...Object.keys(data).length ? data : {}
-      };
-      return JSON.stringify(errorDetails, null, 2);
-    }
-    if (data instanceof Map) {
-      data = Object.fromEntries(data);
+    if (typeof data === "string") {
+      return data;
     }
-    return typeof data === "object" ? JSON.stringify(data, null, 2) : String(data);
+    return inspect(data, { depth: null, colors: false });
   }
   log(message, data) {
     console.log(source_default.white(`
@@ -41023,10 +41016,12 @@ ${message}`));
   }
   succeedSpinner(message, data) {
     if (data !== void 0) this.log("Result:", data);
+    console.log("");
     this.spinner.succeed(source_default.green(message));
   }
   failSpinner(message, error) {
     if (error) this.log("Error:", error);
+    console.log("");
     this.spinner.fail(source_default.red(message));
   }
   stopSpinner() {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "genlayer",
-  "version": "0.18.2",
+  "version": "0.18.4",
   "description": "GenLayer Command Line Tool",
   "main": "src/index.ts",
   "type": "module",

package/src/lib/actions/BaseAction.ts

@@ -2,6 +2,7 @@ import {ConfigFileManager} from "../../lib/config/ConfigFileManager";
 import ora, {Ora} from "ora";
 import chalk from "chalk";
 import inquirer from "inquirer";
+import { inspect } from "util";
 import {KeypairManager} from "../accounts/KeypairManager";
 import {createClient, createAccount} from "genlayer-js";
 import {localnet} from "genlayer-js/chains";
@@ -58,20 +59,10 @@ export class BaseAction extends ConfigFileManager {
   }
 
   private formatOutput(data: any): string {
-    if (data instanceof Error) {
-      const errorDetails = {
-        name: data.name,
-        message: data.message,
-        ...(Object.keys(data).length ? data : {}),
-      };
-      return JSON.stringify(errorDetails, null, 2);
+    if (typeof data === "string") {
+      return data;
     }
-
-    if (data instanceof Map) {
-      data = Object.fromEntries(data);
-    }
-
-    return typeof data === "object" ? JSON.stringify(data, null, 2) : String(data);
+    return inspect(data, { depth: null, colors: false });
   }
 
   protected log(message: string, data?: any): void {
@@ -106,11 +97,13 @@ export class BaseAction extends ConfigFileManager {
 
   protected succeedSpinner(message: string, data?: any): void {
     if (data !== undefined) this.log("Result:", data);
+    console.log('');
     this.spinner.succeed(chalk.green(message));
   }
 
-  protected failSpinner(message: string, error?: any): void {
+  protected failSpinner(message: string, error?:any): void {
     if (error) this.log("Error:", error);
+    console.log('');
     this.spinner.fail(chalk.red(message));
   }
 
@@ -121,4 +114,4 @@ export class BaseAction extends ConfigFileManager {
   protected setSpinnerText(message: string): void {
     this.spinner.text = chalk.blue(message);
   }
-}
+}

package/tests/libs/baseAction.test.ts

@@ -3,6 +3,7 @@ import {BaseAction} from "../../src/lib/actions/BaseAction";
 import inquirer from "inquirer";
 import ora, {Ora} from "ora";
 import chalk from "chalk";
+import {inspect} from "util";
 
 vi.mock("inquirer");
 vi.mock("ora");
@@ -42,11 +43,17 @@ describe("BaseAction", () => {
 
   test("should succeed the spinner with a message", () => {
     baseAction["succeedSpinner"]("Success");
+    expect(consoleSpy).toHaveBeenCalledWith("");
     expect(mockSpinner.succeed).toHaveBeenCalledWith(expect.stringContaining("Success"));
   });
 
   test("should fail the spinner with an error message", () => {
-    baseAction["failSpinner"]("Failure", new Error("Something went wrong"));
+    const error = new Error("Something went wrong");
+    baseAction["failSpinner"]("Failure", error);
+
+    expect(consoleSpy).toHaveBeenCalledWith(expect.stringContaining("Error:"));
+    expect(consoleSpy).toHaveBeenCalledWith(inspect(error, {depth: null, colors: false}));
+    expect(consoleSpy).toHaveBeenCalledWith("");
     expect(mockSpinner.fail).toHaveBeenCalledWith(expect.stringContaining("Failure"));
   });
 
@@ -108,7 +115,7 @@ describe("BaseAction", () => {
     baseAction["logSuccess"]("Success message", data);
 
     expect(consoleSpy).toHaveBeenCalledWith(expect.stringContaining("✔ Success message"));
-    expect(consoleSpy).toHaveBeenCalledWith(chalk.green(JSON.stringify(data, null, 2)));
+    expect(consoleSpy).toHaveBeenCalledWith(chalk.green(inspect(data, {depth: null, colors: false})));
   });
 
   test("should log an error message with error details", () => {
@@ -117,18 +124,7 @@ describe("BaseAction", () => {
     baseAction["logError"]("Error message", error);
 
     expect(consoleErrorSpy).toHaveBeenCalledWith(expect.stringContaining("✖ Error message"));
-    expect(consoleErrorSpy).toHaveBeenCalledWith(
-      chalk.red(
-        JSON.stringify(
-          {
-            name: error.name,
-            message: error.message,
-          },
-          null,
-          2,
-        ),
-      ),
-    );
+    expect(consoleErrorSpy).toHaveBeenCalledWith(chalk.red(inspect(error, {depth: null, colors: false})));
   });
 
   test("should log an info message with data", () => {
@@ -137,7 +133,7 @@ describe("BaseAction", () => {
     baseAction["logInfo"]("Info message", data);
 
     expect(consoleSpy).toHaveBeenCalledWith(expect.stringContaining("ℹ Info message"));
-    expect(consoleSpy).toHaveBeenCalledWith(chalk.blue(JSON.stringify(data, null, 2)));
+    expect(consoleSpy).toHaveBeenCalledWith(chalk.blue(inspect(data, {depth: null, colors: false})));
   });
 
   test("should log a warning message with data", () => {
@@ -146,7 +142,7 @@ describe("BaseAction", () => {
     baseAction["logWarning"]("Warning message", data);
 
     expect(consoleSpy).toHaveBeenCalledWith(expect.stringContaining("⚠ Warning message"));
-    expect(consoleSpy).toHaveBeenCalledWith(chalk.yellow(JSON.stringify(data, null, 2)));
+    expect(consoleSpy).toHaveBeenCalledWith(chalk.yellow(inspect(data, {depth: null, colors: false})));
   });
 
   test("should succeed the spinner with a message and log result if data is provided", () => {
@@ -155,52 +151,17 @@ describe("BaseAction", () => {
     baseAction["succeedSpinner"]("Success", mockData);
 
     expect(consoleSpy).toHaveBeenCalledWith(expect.stringContaining("Result:"));
-    expect(consoleSpy).toHaveBeenCalledWith(JSON.stringify(mockData, null, 2));
+    expect(consoleSpy).toHaveBeenCalledWith(inspect(mockData, {depth: null, colors: false}));
+    expect(consoleSpy).toHaveBeenCalledWith("");
     expect(mockSpinner.succeed).toHaveBeenCalledWith(expect.stringContaining("Success"));
   });
 
-  test("should format an Error instance with name, message, and additional properties", () => {
-    const error = new Error("Something went wrong");
-    (error as any).code = 500;
-
-    const result = (baseAction as any).formatOutput(error);
-    expect(result).toBe(JSON.stringify({name: "Error", message: "Something went wrong", code: 500}, null, 2));
-  });
-
-  test("should format an object as JSON string", () => {
-    const data = {key: "value", num: 42};
-    const result = (baseAction as any).formatOutput(data);
-
-    expect(result).toBe(JSON.stringify(data, null, 2));
-  });
-
   test("should return a string representation of a primitive", () => {
     expect((baseAction as any).formatOutput("Hello")).toBe("Hello");
     expect((baseAction as any).formatOutput(42)).toBe("42");
     expect((baseAction as any).formatOutput(true)).toBe("true");
   });
 
-  test("should format a Map object correctly", () => {
-    const testMap = new Map<string, any>([
-      ["key1", "value1"],
-      ["key2", 42],
-      ["key3", {nested: "object"}],
-    ]);
-
-    const result = (baseAction as any).formatOutput(testMap);
-    const expected = JSON.stringify(
-      {
-        key1: "value1",
-        key2: 42,
-        key3: {nested: "object"},
-      },
-      null,
-      2,
-    );
-
-    expect(result).toBe(expected);
-  });
-
   const mockPrivateKey = "mocked_private_key";
 
   beforeEach(() => {
@@ -240,4 +201,34 @@ describe("BaseAction", () => {
 
     await expect(baseAction["getPrivateKey"]()).rejects.toThrow("process exited");
   });
+
+  describe("formatOutput", () => {
+    test("should return string as is", () => {
+      expect((baseAction as any).formatOutput("Hello")).toBe("Hello");
+    });
+
+    test("should format an object", () => {
+      const data = {key: "value", num: 42};
+      const result = (baseAction as any).formatOutput(data);
+      expect(result).toBe("{ key: 'value', num: 42 }");
+    });
+
+    test("should format an error object", () => {
+      const error = new Error("Test Error");
+      const result = (baseAction as any).formatOutput(error);
+      expect(result).toContain("Error: Test Error");
+    });
+
+    test("should format a Map object", () => {
+      const testMap = new Map([["key1", "value1"]]);
+      const result = (baseAction as any).formatOutput(testMap);
+      expect(result).toBe("Map(1) { 'key1' => 'value1' }");
+    });
+
+    test("should format a BigInt object", () => {
+      const bigIntValue = BigInt(9007199254740991);
+      const result = (baseAction as any).formatOutput(bigIntValue);
+      expect(result).toBe("9007199254740991n");
+    });
+  });
 });