
Mirlo worked extensively on the near/near-api-js repository, delivering 69 features and 39 bug fixes over 13 months. He focused on modularizing the API, improving type safety, and enhancing error handling to support robust blockchain integrations. Using TypeScript and JavaScript, Mirlo introduced type-safe contract abstractions, concurrent transaction support, and comprehensive RPC error classification, which improved reliability and developer experience. His work included modernizing the build process, expanding end-to-end testing, and consolidating legacy packages for maintainability. By refining API surfaces and automating release workflows, Mirlo enabled safer migrations and streamlined onboarding for developers building wallets and dApps on NEAR Protocol.
Month 2026-01 – Near API JS: Key deliverables, impact, and learnings. Overview: This month focused on strengthening error handling, expanding API capabilities, and improving resilience across near-api-js. The work emphasizes business value through clearer failure signals, safer transaction flows, and more flexible integration points for clients. Key outcomes: - Robust error handling overhaul: Introduced a comprehensive set of type-safe RPC error types, replacing the old TypedError with specific errors (UnknownBlockError, InternalRpcError, plus a suite of per-RPC errors). This enables precise error classification, better UX for developers, and more reliable retry/handling logic in client apps. Tests were updated to cover AccountAlreadyExistsError and related failure modes. - Concurrency and API flexibility: Added concurrent transactions support and extended the Account constructor to accept an RPC URL string in addition to Provider, increasing flexibility for different deployment topologies and throughput. Provider.query overload cleanup and viewGlobalContractCode method were added to streamline contract interactions. - RPC error exposure and HTTP resilience: Exported RPC errors behind a dedicated rpc-errors path for easier discovery and integration; improved HTTP error handling for 502/429 responses; ensured only 5xx and timeout conditions are treated as fetchJsonRpc errors, reducing false positives. - Quality, consistency, and maintenance: Seed phrase parsing (parseSeedPhrase) added; removed outdated error utilities; renamed TypedContract back to Contract for consistency; pre-release mode exited; typecheck checks extended to test and e2e folders; tests updated to reflect new error names and parsing semantics. Impact: The changes reduce failure ambiguity, accelerate integration timelines for client apps, and increase system reliability under load. Developers benefit from precise error signals, safer transaction flows, and broader API surface for building robust wallets and dApps.
Month 2026-01 – Near API JS: Key deliverables, impact, and learnings. Overview: This month focused on strengthening error handling, expanding API capabilities, and improving resilience across near-api-js. The work emphasizes business value through clearer failure signals, safer transaction flows, and more flexible integration points for clients. Key outcomes: - Robust error handling overhaul: Introduced a comprehensive set of type-safe RPC error types, replacing the old TypedError with specific errors (UnknownBlockError, InternalRpcError, plus a suite of per-RPC errors). This enables precise error classification, better UX for developers, and more reliable retry/handling logic in client apps. Tests were updated to cover AccountAlreadyExistsError and related failure modes. - Concurrency and API flexibility: Added concurrent transactions support and extended the Account constructor to accept an RPC URL string in addition to Provider, increasing flexibility for different deployment topologies and throughput. Provider.query overload cleanup and viewGlobalContractCode method were added to streamline contract interactions. - RPC error exposure and HTTP resilience: Exported RPC errors behind a dedicated rpc-errors path for easier discovery and integration; improved HTTP error handling for 502/429 responses; ensured only 5xx and timeout conditions are treated as fetchJsonRpc errors, reducing false positives. - Quality, consistency, and maintenance: Seed phrase parsing (parseSeedPhrase) added; removed outdated error utilities; renamed TypedContract back to Contract for consistency; pre-release mode exited; typecheck checks extended to test and e2e folders; tests updated to reflect new error names and parsing semantics. Impact: The changes reduce failure ambiguity, accelerate integration timelines for client apps, and increase system reliability under load. Developers benefit from precise error signals, safer transaction flows, and broader API surface for building robust wallets and dApps.
December 2025 monthly summary for near/near-api-js: Delivered core product improvements focused on modular imports, API consistency, and developer tooling, underpinned by expanded test coverage and code quality improvements. The work enhances bundle size, developer experience, and runtime efficiency, enabling faster feature delivery and safer API evolution.
December 2025 monthly summary for near/near-api-js: Delivered core product improvements focused on modular imports, API consistency, and developer tooling, underpinned by expanded test coverage and code quality improvements. The work enhances bundle size, developer experience, and runtime efficiency, enabling faster feature delivery and safer API evolution.
November 2025 (near-api-js): Delivered major CI and repository modernization, consolidated legacy packages, and implemented comprehensive testing and quality improvements to increase release velocity, reliability, and developer productivity. Highlights include a unified codebase, stricter typing (TypeScript strict mode), API consistency (object-argument style), new automation scripts, and expanded automated testing coverage. These changes reduce maintenance overhead and improve fault detection across PRs and releases, delivering tangible business value through faster, safer releases and a more robust developer experience.
November 2025 (near-api-js): Delivered major CI and repository modernization, consolidated legacy packages, and implemented comprehensive testing and quality improvements to increase release velocity, reliability, and developer productivity. Highlights include a unified codebase, stricter typing (TypeScript strict mode), API consistency (object-argument style), new automation scripts, and expanded automated testing coverage. These changes reduce maintenance overhead and improve fault detection across PRs and releases, delivering tangible business value through faster, safer releases and a more robust developer experience.
October 2025 monthly summary for near/near-api-js focusing on reliability, binary data support, and release readiness. Highlights include targeted fixes to the FailoverRpcProvider, expansion of contract call inputs to Uint8Array, and introduction of a changeset-based release process. These changes improve failover reliability, broaden contract interaction capabilities, and streamline versioning for consumers.
October 2025 monthly summary for near/near-api-js focusing on reliability, binary data support, and release readiness. Highlights include targeted fixes to the FailoverRpcProvider, expansion of contract call inputs to Uint8Array, and introduction of a changeset-based release process. These changes improve failover reliability, broaden contract interaction capabilities, and streamline versioning for consumers.
Month 2025-09 highlights for near-api-js focusing on business value and technical craftsmanship. Key outcomes include end-to-end biometric Ed25519 support with API exposure, type-safety improvements in editor typings, enhanced PR governance via conventional-commit enforcement, and proactive test-suite cleanup. These efforts reduce integration risk, improve developer velocity, and set a solid foundation for reliable releases.
Month 2025-09 highlights for near-api-js focusing on business value and technical craftsmanship. Key outcomes include end-to-end biometric Ed25519 support with API exposure, type-safety improvements in editor typings, enhanced PR governance via conventional-commit enforcement, and proactive test-suite cleanup. These efforts reduce integration risk, improve developer velocity, and set a solid foundation for reliable releases.
Month 2025-08: Delivered core improvements to near-api-js focused on type safety, API stability, and migration readiness. Implemented a set of proactive reliability fixes, introduced a TypedContract path for safer contract interactions, and established deprecation guidelines with runtime warnings to guide developers through upcoming API removals. End-to-end RPC nonce-stability tests validate behavior for consecutive transfers, reducing risk in production deployments. Collectively, these changes enhance developer productivity, reduce runtime errors, and support scalable adoption of the API upgrades.
Month 2025-08: Delivered core improvements to near-api-js focused on type safety, API stability, and migration readiness. Implemented a set of proactive reliability fixes, introduced a TypedContract path for safer contract interactions, and established deprecation guidelines with runtime warnings to guide developers through upcoming API removals. End-to-end RPC nonce-stability tests validate behavior for consecutive transfers, reducing risk in production deployments. Collectively, these changes enhance developer productivity, reduce runtime errors, and support scalable adoption of the API upgrades.
July 2025 monthly summary for near/near-api-js focusing on delivering type-safe API improvements, fixing finality checks, and enabling release tooling. Key business value includes improved reliability of account function calls, stronger type guarantees across Provider and Account APIs, and streamlined release processes with tests for meta-transactions.
July 2025 monthly summary for near/near-api-js focusing on delivering type-safe API improvements, fixing finality checks, and enabling release tooling. Key business value includes improved reliability of account function calls, stronger type guarantees across Provider and Account APIs, and streamlined release processes with tests for meta-transactions.
June 2025 monthly summary for near-api-js: Delivered build and packaging modernization, API stability improvements, and expanded testing and release tooling. This work drove faster, smaller bundles, stronger API guarantees, automated quality checks, and streamlined multi-package releases, aligning technical outcomes with business value.
June 2025 monthly summary for near-api-js: Delivered build and packaging modernization, API stability improvements, and expanded testing and release tooling. This work drove faster, smaller bundles, stronger API guarantees, automated quality checks, and streamlined multi-package releases, aligning technical outcomes with business value.
May 2025 monthly summary for near/near-api-js focused on API simplification, reliability, and release automation. The team delivered a cleaner API surface for Account and FT interactions, modernized account creation flows with sub-account support, and strengthened testing and release tooling for stability and maintenance. Key features delivered: - API surface cleanup and enhancements for account and fungible token interactions, including optional parameters in Account.callFunction, removal of outdated APIs, and new FT utilities. Notable changes include removing transferNEAR in favor of transferToken, adding register/unregister with callbacks, and updating related account/FT flows. - Account creation API modernization, renaming and restructuring for clarity and sub-account support; make the createAccount interface universal. - Testing, release, and maintenance automation improvements to enhance stability, including optimistic finality defaults in tests, graceful workspace shutdown, and changeset/CI tooling refinements. Major bugs fixed: - ft_balance_of bug that returned undefined for FungibleToken is resolved; API balance retrieval now returns correct values. - Deprecations and cleanup of older API paths (Connection, connect) to reduce surface area and improve future migrations. Overall impact and accomplishments: - Improved developer experience and onboarding with a cleaner, more predictable API surface and safer defaults. - Enhanced reliability of account/FT operations and more robust test/release processes, enabling faster and safer deployments. Technologies/skills demonstrated: - TypeScript/JavaScript API design and deprecation strategy - API modernization for accounts and fungible tokens - Testing strategies for near RPC and sandbox environments, including default finality and graceful shutdowns - Release automation, changesets, CI/CD improvements, and package management
May 2025 monthly summary for near/near-api-js focused on API simplification, reliability, and release automation. The team delivered a cleaner API surface for Account and FT interactions, modernized account creation flows with sub-account support, and strengthened testing and release tooling for stability and maintenance. Key features delivered: - API surface cleanup and enhancements for account and fungible token interactions, including optional parameters in Account.callFunction, removal of outdated APIs, and new FT utilities. Notable changes include removing transferNEAR in favor of transferToken, adding register/unregister with callbacks, and updating related account/FT flows. - Account creation API modernization, renaming and restructuring for clarity and sub-account support; make the createAccount interface universal. - Testing, release, and maintenance automation improvements to enhance stability, including optimistic finality defaults in tests, graceful workspace shutdown, and changeset/CI tooling refinements. Major bugs fixed: - ft_balance_of bug that returned undefined for FungibleToken is resolved; API balance retrieval now returns correct values. - Deprecations and cleanup of older API paths (Connection, connect) to reduce surface area and improve future migrations. Overall impact and accomplishments: - Improved developer experience and onboarding with a cleaner, more predictable API surface and safer defaults. - Enhanced reliability of account/FT operations and more robust test/release processes, enabling faster and safer deployments. Technologies/skills demonstrated: - TypeScript/JavaScript API design and deprecation strategy - API modernization for accounts and fungible tokens - Testing strategies for near RPC and sandbox environments, including default finality and graceful shutdowns - Release automation, changesets, CI/CD improvements, and package management
April 2025 near-api-js delivered a broad expansion of the API surface, tighter signer integration, and enhanced account capabilities, while strengthening test stability and package consistency. The focus was on enabling end-to-end signer flows, expanding provider capabilities for richer dApp integrations, beefing up account creation workflows, and laying groundwork for token tooling. Business value includes easier developer onboarding, safer signing flows, more complete RPC coverage, and consistent, maintainable packages across the mono-repo.
April 2025 near-api-js delivered a broad expansion of the API surface, tighter signer integration, and enhanced account capabilities, while strengthening test stability and package consistency. The focus was on enabling end-to-end signer flows, expanding provider capabilities for richer dApp integrations, beefing up account creation workflows, and laying groundwork for token tooling. Business value includes easier developer onboarding, safer signing flows, more complete RPC coverage, and consistent, maintainable packages across the mono-repo.
March 2025 monthly summary for near-api-js focused on delivering foundational account and contract interaction improvements and preparing the SDK for easier long-term maintenance and usage. Key feature work centered on introducing comprehensive abstractions for Signer, Account, and Contract v2, enabling more robust and ergonomic account-based interactions with contracts and on-chain signing. Major highlights include the design and implementation of new abstractions in account_v2.ts and account_v2.js, introducing PublicAccountV2, ContractV2, and SignerAccountV2 to manage account information, contract calls, and transaction signing. This work sets a stable, reusable foundation for higher-level SDK features and migration to v2 APIs. Business value: reduced boilerplate for developers, streamlined signing flows, and improved consistency across account and contract interactions, accelerating integration efforts for client apps and wallets. Technologies/skills demonstrated: TypeScript/JavaScript module design, API/abstraction design, refactoring, on-chain interaction patterns, and secure signing workflows.
March 2025 monthly summary for near-api-js focused on delivering foundational account and contract interaction improvements and preparing the SDK for easier long-term maintenance and usage. Key feature work centered on introducing comprehensive abstractions for Signer, Account, and Contract v2, enabling more robust and ergonomic account-based interactions with contracts and on-chain signing. Major highlights include the design and implementation of new abstractions in account_v2.ts and account_v2.js, introducing PublicAccountV2, ContractV2, and SignerAccountV2 to manage account information, contract calls, and transaction signing. This work sets a stable, reusable foundation for higher-level SDK features and migration to v2 APIs. Business value: reduced boilerplate for developers, streamlined signing flows, and improved consistency across account and contract interactions, accelerating integration efforts for client apps and wallets. Technologies/skills demonstrated: TypeScript/JavaScript module design, API/abstraction design, refactoring, on-chain interaction patterns, and secure signing workflows.
January 2025: WalletSelector revamp delivering standardized WalletManager API, cohesive integration, and API surface cleanup, backed by unit tests. This set the foundation for scalable and reliable wallet flows across the NEAR ecosystem.
January 2025: WalletSelector revamp delivering standardized WalletManager API, cohesive integration, and API surface cleanup, backed by unit tests. This set the foundation for scalable and reliable wallet flows across the NEAR ecosystem.
December 2024 performance: delivered a dependency-management enhancement for near/wallet-selector by switching near-api-js to a peerDependency with a version range, improving cross-project compatibility and reducing integration conflicts. No major bugs reported; this change enhances stability, reproducibility, and ease of downstream upgrades, aligning with CI and packaging best practices.
December 2024 performance: delivered a dependency-management enhancement for near/wallet-selector by switching near-api-js to a peerDependency with a version range, improving cross-project compatibility and reducing integration conflicts. No major bugs reported; this change enhances stability, reproducibility, and ease of downstream upgrades, aligning with CI and packaging best practices.

Overview of all repositories you've contributed to across your timeline