Tossbank Reveals Three Core Standards for Package Development: Stability, Predictability, and Debugging Convenience

Tossbank's Technology Group introduced three standards—Stability, Predictability, and Debugging Convenience—to improve the package development environment. Previously, hosts had to separately verify a package's supported browsers and API compatibility, but these standards clearly delineate the roles of package creators and users.

Ensuring Stability and Predictability

Packages must operate reliably within the host's execution environment, and the intent of the original code must be preserved even after deployment. Tossbank decided to deploy packages while maintaining their JavaScript syntax and module structure as much as possible. Syntax transformation and final bundling are handled by the host, which knows the scope of each service's support, preventing unnecessary code transformations or file boundary damage. For example, the original module structure is passed through to ensure that file-level boundaries, such as the 'use client' directive in Next.js App Router, are not broken during the bundling process.

Enhancing Debugging Convenience

Declaration sourcemaps are supported to make it easier to identify package issues at the usage site. This file links .d.ts declarations to their original source code locations, allowing developers to view the actual implementation code instead of just type declarations with a single click in their IDE. This enables direct verification of function error conditions and option behaviors without relying solely on type information.