Files

1.2 KiB

KriFrontCommon Package and Runtime Contract

  • Use the package root for runtime-neutral object, URL, date, string, and shared type utilities.
  • Use a focused subpath such as @kri/common/http, @kri/common/browser, @kri/common/server, @kri/common/security, @kri/common/hooks, @kri/common/query, @kri/common/config, @kri/common/jotai, or @kri/common/noti-hub for the corresponding capability.
  • Keep browser, server, and runtime-neutral imports on their intended side of the application boundary.
  • A consumer that uses React hooks, TanStack Query, or Jotai integrations must provide the compatible optional peer dependency required by its selected entry point.
  • Preserve the project's established HTTP client, authentication, error-policy, query-client, storage, and environment conventions when adopting a shared helper.
  • Validate external data at runtime; a shared TypeScript type alone does not validate an API response or persisted value.
  • Prefer named public exports and retain the consumer project's current module system and bundler conventions.