@cp949/japanpost-react 1.0.1 → 1.0.2

package/README.ko.md

@@ -169,8 +169,10 @@ export function PostalForm() {
 - `useJapanAddress`
 - `PostalCodeInput`
 - `AddressSearchInput`
-- `JapanAddress`, `JapanAddressDataSource`, `JapanPostSearchcodeRequest`,
-  `JapanPostAddresszipRequest`, `Page`를 포함한 공개 타입
+- `JapanAddress`, `JapanAddressDataSource`, `JapanPostalCodeSearchInput`,
+  `JapanAddressSearchInput`, `JapanPostSearchcodeRequest`,
+  `JapanPostAddresszipRequest`, `Page`를 포함한
+  공개 타입
 - 요청 옵션 타입: `JapanAddressRequestOptions`
 
 ## 유틸리티 메모
@@ -182,56 +184,94 @@ export function PostalForm() {
 
 ### useJapanPostalCode
 
-우편번호로 주소를 조회합니다. `3~7자리` 숫자 입력을 받아 `3~6자리`일 때는
-prefix 검색으로 동작합니다.
+우편번호로 주소를 조회합니다. 문자열 입력과 구조화된 요청 입력을 모두
+받을 수 있고, `3~6자리` 입력일 때는 prefix 검색으로 동작합니다.
 
 ```tsx
-const { loading, data, error, search, reset } = useJapanPostalCode({
+const { loading, data, error, search, cancel, reset } = useJapanPostalCode({
   dataSource,
 });
 ```
 
+```tsx
+void search("1000001");
+void search({
+  postalCode: "1000001",
+  pageNumber: 1,
+  rowsPerPage: 10,
+  includeParenthesesTown: true,
+});
+```
+
+`cancel()`은 진행 중인 조회를 중단하고 현재 data/error 상태는 그대로 유지합니다.
+`reset()`은 `cancel()`을 호출한 뒤 data/error까지 비워 훅을 idle 상태로
+되돌립니다.
+
 ### useJapanAddressSearch
 
-자유 형식 키워드로 주소를 검색하며 `debounceMs`를 지원합니다.
+자유 형식 키워드 또는 구조화된 필드로 주소를 검색하며 `debounceMs`를 지원합니다.
 
 ```tsx
-const { loading, data, error, search, reset } = useJapanAddressSearch({
+const { loading, data, error, search, cancel, reset } = useJapanAddressSearch({
   dataSource,
   debounceMs: 300,
 });
 ```
 
+```tsx
+void search("Tokyo");
+void search({
+  addressQuery: "Tokyo",
+  pageNumber: 1,
+  rowsPerPage: 10,
+  includeCityDetails: true,
+});
+void search({
+  prefName: "東京都",
+  cityName: "千代田区",
+});
+```
+
+`search("Tokyo")`는 `addressQuery` 검색의 축약형입니다. 구조화된 필드는
+`addressQuery` 없이도 사용할 수 있어서, 도도부현/시/동 단위로만 검색하고 싶을 때
+유용합니다.
+
 이 훅은 빈 검색어에 대해 여전히 클라이언트 선제 검증을 수행하고, 요청을 보내기
 전에 `invalid_query`를 반환합니다. 이 검증은 UX 보조 장치이며 서버 검증이나
 서버 계약 처리를 대체하지 않습니다.
 
+`cancel()`은 진행 중인 요청이나 대기 중인 debounce 타이머를 중단하고,
+현재 data/error 상태는 그대로 유지합니다. `reset()`은 `cancel()`을 호출한 뒤
+data와 error까지 비워 훅을 idle 상태로 되돌립니다.
+
 ### useJapanAddress
 
-우편번호 조회와 키워드 검색을 하나의 훅으로 합칩니다.
+우편번호 조회와 주소 질의 검색을 하나의 훅으로 합칩니다.
 
 ```tsx
-const { loading, data, error, searchByPostalCode, searchByKeyword, reset } =
+const { loading, data, error, searchByPostalCode, searchByAddressQuery, reset } =
   useJapanAddress({ dataSource, debounceMs: 300 });
 ```
 
 모든 훅은 런타임에서 `dataSource`가 필요합니다.
 
-훅의 public API는 계속 문자열 기반입니다.
+`useJapanPostalCode().search`, `useJapanAddressSearch().search`,
+`useJapanAddress`의 편의 메서드는 모두 같은 공개 검색 입력 타입을 받습니다.
 
-- `useJapanPostalCode().search(value: string)`
-- `useJapanAddressSearch().search(query: string)`
-- `useJapanAddress().searchByPostalCode(value: string)`
-- `useJapanAddress().searchByKeyword(query: string)`
+- `useJapanPostalCode().search(input: JapanPostalCodeSearchInput)`
+- `useJapanAddressSearch().search(input: JapanAddressSearchInput)`
+- `useJapanAddress().searchByPostalCode(input: JapanPostalCodeSearchInput)`
+- `useJapanAddress().searchByAddressQuery(input: JapanAddressSearchInput)`
 
 대신 훅 내부에서 `dataSource` 호출 전에 request object를 조립합니다.
 
-- 우편번호 조회: `{ value, pageNumber: 0, rowsPerPage: 100 }`
-- 주소 검색: `{ freeword, pageNumber: 0, rowsPerPage: 100 }`
+- 우편번호 조회: `{ postalCode, pageNumber: 0, rowsPerPage: 100 }`
+- 주소 검색: `{ addressQuery, pageNumber: 0, rowsPerPage: 100 }`
 
-`includeCityDetails`, `includePrefectureDetails` 같은 optional flag는
-기본적으로 넣지 않으며, 필요하면 사용자 data source 구현에서 직접
-지정하면 됩니다.
+`useJapanAddressSearch`에서는 `addressQuery`를 생략한 구조화 요청도 가능하므로
+도도부현, 시, 동 필드만으로 검색할 수 있습니다. `includeCityDetails`,
+`includePrefectureDetails` 같은 optional flag는 기본적으로 넣지 않으며,
+필요하면 사용자 data source 구현에서 직접 지정하면 됩니다.
 
 ## 에러 처리 메모
 
@@ -248,9 +288,9 @@ type JapanAddressRequestOptions = {
 };
 ```
 
-훅은 superseded 요청, `reset()`, unmount 정리 상황에서 이전 요청을 취소할 수
-있도록 `signal`을 전달합니다. 백엔드 레이어가 abort를 지원하면 그대로 활용할 수
-있습니다.
+훅은 superseded 요청, `cancel()`, `reset()`, unmount 정리 상황에서 이전
+요청을 취소할 수 있도록 `signal`을 전달합니다. 백엔드 레이어가 abort를 지원하면
+그대로 활용할 수 있습니다.
 
 권장 에러 코드 매핑:
 

package/README.md

@@ -4,12 +4,11 @@
 
 <!-- This file is generated by `pnpm readme:package`. Edit docs/README.en.md and docs/README.ko.md instead. -->
 
-React + TypeScript hooks and headless inputs for Japan postal-code and address
-lookup.
+React hooks, headless input components, and utilities for Japan postal-code
+and address lookup.
 
-This package guide covers the published library. Repository-level demo scripts
-such as `pnpm demo:full` currently target Linux/WSL-style shell environments
-and are documented in the root README.
+This package does not call Japan Post directly. You provide a
+`JapanAddressDataSource` that talks to your own backend API.
 
 ## Install
 
@@ -17,45 +16,56 @@ and are documented in the root README.
 pnpm add @cp949/japanpost-react
 ```
 
-- Supported React versions: React 18 and React 19
+- Peer dependencies: React 18 or React 19
+- Package source in this repository:
+  `packages/japanpost-react`
+- Demo app in this repository: `apps/demo`
+
+## What The Package Provides
+
+- Hooks for postal-code lookup and address search:
+  `useJapanPostalCode`, `useJapanAddressSearch`, `useJapanAddress`
+- Headless form components:
+  `PostalCodeInput`, `AddressSearchInput`
+- Utilities:
+  `normalizeJapanPostalCode`, `formatJapanPostalCode`,
+  `isValidJapanPostalCode`, `normalizeJapanPostAddressRecord`,
+  `createJapanAddressError`
+- Public types for the request, response, error, and data-source contracts
 
 ## Quick Start
 
+The package expects a `JapanAddressDataSource` with two methods:
+
+- `lookupPostalCode(request, options?)`
+- `searchAddress(request, options?)`
+
+Both methods return `Promise<Page<JapanAddress>>`.
+
 ```tsx
-import { useJapanPostalCode } from "@cp949/japanpost-react";
-import type {
-  JapanAddressDataSource,
-  JapanAddressRequestOptions,
-  JapanAddress,
-  Page,
+import {
+  PostalCodeInput,
+  createJapanAddressError,
+  useJapanPostalCode,
+  type JapanAddress,
+  type JapanAddressDataSource,
+  type JapanAddressRequestOptions,
+  type Page,
 } from "@cp949/japanpost-react";
-import { createJapanAddressError } from "@cp949/japanpost-react";
 
-// The only supported integration model is a real server-backed flow.
-// Point the data source at your own backend API.
-// On beta-compatible backends, blank addresszip searches and postal-code misses
-// may return HTTP 200 with an empty page. Keep those as successful Page results.
-// The status mapping below applies only to non-OK responses.
 function isAbortError(error: unknown): boolean {
   return error instanceof DOMException && error.name === "AbortError";
 }
 
-function resolveErrorCode(path: string, status: number) {
-  if (status === 404) {
-    return "not_found";
-  }
-
-  if (status === 504) {
-    return "timeout";
-  }
-
-  if (status === 400) {
-    return path === "/q/japanpost/searchcode"
-      ? "invalid_postal_code"
-      : "invalid_query";
-  }
-
-  return "data_source_error";
+function isPagePayload(payload: unknown): payload is Page<JapanAddress> {
+  return (
+    typeof payload === "object" &&
+    payload !== null &&
+    Array.isArray((payload as { elements?: unknown }).elements) &&
+    typeof (payload as { totalElements?: unknown }).totalElements === "number" &&
+    typeof (payload as { pageNumber?: unknown }).pageNumber === "number" &&
+    typeof (payload as { rowsPerPage?: unknown }).rowsPerPage === "number"
+  );
 }
 
 async function readPage(
@@ -63,10 +73,10 @@ async function readPage(
   request: unknown,
   options?: JapanAddressRequestOptions,
 ): Promise<Page<JapanAddress>> {
-  let res: Response;
+  let response: Response;
 
   try {
-    res = await fetch(path, {
+    response = await fetch(path, {
       method: "POST",
       headers: {
         "content-type": "application/json",
@@ -78,173 +88,213 @@ async function readPage(
     throw createJapanAddressError(
       isAbortError(error) ? "timeout" : "network_error",
       isAbortError(error) ? "Request timed out" : "Network request failed",
-      {
-        cause: error,
-      },
+      { cause: error },
     );
   }
 
-  if (!res.ok) {
-    const message = `Request failed with status ${res.status}`;
-
-    throw createJapanAddressError(resolveErrorCode(path, res.status), message, {
-      status: res.status,
-    });
+  if (!response.ok) {
+    throw createJapanAddressError(
+      "data_source_error",
+      `Request failed with status ${response.status}`,
+      { status: response.status },
+    );
   }
 
   let payload: unknown;
 
   try {
-    payload = await res.json();
+    payload = await response.json();
   } catch (error) {
     throw createJapanAddressError(
       "bad_response",
       "Response payload was not valid JSON",
-      {
-        cause: error,
-      },
+      { cause: error },
     );
   }
 
-  if (
-    typeof payload !== "object" ||
-    payload === null ||
-    !Array.isArray((payload as { elements?: unknown }).elements) ||
-    typeof (payload as { totalElements?: unknown }).totalElements !== "number" ||
-    typeof (payload as { pageNumber?: unknown }).pageNumber !== "number" ||
-    typeof (payload as { rowsPerPage?: unknown }).rowsPerPage !== "number"
-  ) {
+  if (!isPagePayload(payload)) {
     throw createJapanAddressError(
       "bad_response",
       "Response payload must include a valid page payload",
     );
   }
 
-  return payload as Page<JapanAddress>;
+  return payload;
 }
 
 const dataSource: JapanAddressDataSource = {
-  async lookupPostalCode(request, options) {
-    return readPage(`/q/japanpost/searchcode`, request, options);
+  lookupPostalCode(request, options) {
+    return readPage("/q/japanpost/searchcode", request, options);
   },
-  async searchAddress(request, options) {
-    return readPage(`/q/japanpost/addresszip`, request, options);
+  searchAddress(request, options) {
+    return readPage("/q/japanpost/addresszip", request, options);
   },
 };
 
-export function PostalForm() {
+export function PostalCodeLookupExample() {
   const { loading, data, error, search } = useJapanPostalCode({ dataSource });
 
   return (
     <div>
-      <button onClick={() => void search("100-0001")}>Search</button>
-      {loading && <p>Loading...</p>}
-      {error && (
-        <p>
-          {error.code}: {error.message}
-        </p>
-      )}
-      <p>Total results: {data?.totalElements ?? 0}</p>
-      {data?.elements.map((addr) => (
-        <p key={addr.postalCode + addr.address}>{addr.address}</p>
-      ))}
+      <PostalCodeInput
+        buttonLabel="Search"
+        label="Postal code"
+        onSearch={(postalCode) => {
+          void search({ postalCode });
+        }}
+      />
+
+      {loading ? <p>Loading...</p> : null}
+      {error ? <p>{error.message}</p> : null}
+
+      <ul>
+        {(data?.elements ?? []).map((address) => (
+          <li key={`${address.postalCode}-${address.address}`}>
+            {address.address}
+          </li>
+        ))}
+      </ul>
     </div>
   );
 }
 ```
 
-The sample `resolveErrorCode()` helper only classifies non-OK responses. In the
-current beta-compatible contract, blank address-search requests and postal-code
-misses may still succeed with `200` plus an empty page, while `404 -> not_found`
-remains a backend-specific choice for servers that intentionally surface misses
-as errors.
-
-## Exports
-
-- `normalizeJapanPostalCode`
-- `formatJapanPostalCode`
-- `normalizeJapanPostAddressRecord`
-- `isValidJapanPostalCode`
-- `createJapanAddressError`
-- `useJapanPostalCode`
-- `useJapanAddressSearch`
-- `useJapanAddress`
-- `PostalCodeInput`
-- `AddressSearchInput`
-- Public types including `JapanAddress`, `JapanAddressDataSource`,
-  `JapanPostSearchcodeRequest`, `JapanPostAddresszipRequest`, and `Page`
-- Request options type: `JapanAddressRequestOptions`
-
-## Utility Notes
-
-`formatJapanPostalCode()` inserts a hyphen only when the normalized value is
-exactly 7 digits. For any other length, it returns the normalized digits
-without inserting a hyphen.
+The example paths above match this repository's reference backend. In your own
+app, the backend routes can be different as long as your `dataSource`
+implementation returns the same public types.
+
+## Core Contract
+
+`Page<T>` is the result shape shared by the hooks and the reference backend:
+
+```ts
+type Page<T> = {
+  elements: T[];
+  totalElements: number;
+  pageNumber: number;
+  rowsPerPage: number;
+};
+```
+
+`JapanAddress` is the normalized address shape returned by the package:
+
+```ts
+type JapanAddress = {
+  postalCode: string;
+  prefecture: string;
+  prefectureKana?: string;
+  city: string;
+  cityKana?: string;
+  town: string;
+  townKana?: string;
+  address: string;
+  provider: "japan-post";
+};
+```
+
+The hooks keep this page payload as-is, so consumers read
+`data?.elements`, `data?.totalElements`, `data?.pageNumber`, and
+`data?.rowsPerPage` directly.
 
 ## Hooks
 
-### useJapanPostalCode
+### `useJapanPostalCode`
 
-Looks up addresses by postal code. The hook accepts `3-7` digits and uses
-prefix search when the input has `3-6` digits.
+- Accepts `string` or `JapanPostalCodeSearchInput`
+- Normalizes the input to digits before calling the data source
+- Allows `3-7` digits, so prefix lookup is possible
+- Builds `{ postalCode, pageNumber: 0, rowsPerPage: 100 }` by default
+- Exposes `loading`, `data`, `error`, `search`, `cancel`, and `reset`
 
 ```tsx
-const { loading, data, error, search, reset } = useJapanPostalCode({
-  dataSource,
+const postalCode = useJapanPostalCode({ dataSource });
+
+void postalCode.search("100-0001");
+void postalCode.search({
+  postalCode: "1000001",
+  pageNumber: 1,
+  rowsPerPage: 10,
+  includeParenthesesTown: true,
 });
 ```
 
-### useJapanAddressSearch
+### `useJapanAddressSearch`
 
-Searches addresses by free-form keyword and supports debouncing.
+- Accepts `string` or `JapanAddressSearchInput`
+- Supports free-form search and structured fields in the same request type
+- Rejects a fully blank query before calling the data source
+- Omits `includeCityDetails` and `includePrefectureDetails` unless you set them
+- Supports `debounceMs`
+- Exposes `loading`, `data`, `error`, `search`, `cancel`, and `reset`
 
 ```tsx
-const { loading, data, error, search, reset } = useJapanAddressSearch({
+const addressSearch = useJapanAddressSearch({
   dataSource,
   debounceMs: 300,
 });
-```
 
-The hook still performs client-side pre-validation for blank queries and
-returns `invalid_query` before sending a request. That validation is a UX
-helper only and does not replace server-side validation or server-side
-contract handling.
+void addressSearch.search("千代田");
+void addressSearch.search({
+  prefName: "東京都",
+  cityName: "千代田区",
+  pageNumber: 0,
+  rowsPerPage: 10,
+});
+```
 
-### useJapanAddress
+### `useJapanAddress`
 
-Combines postal-code lookup and keyword search into one hook.
+- Combines postal-code lookup and address search in one hook
+- Reuses the same `dataSource`
+- Exposes `searchByPostalCode`, `searchByAddressQuery`, and `reset`
+- Returns `data` and `error` for the currently active search mode only
 
 ```tsx
-const { loading, data, error, searchByPostalCode, searchByKeyword, reset } =
-  useJapanAddress({ dataSource, debounceMs: 300 });
+const address = useJapanAddress({
+  dataSource,
+  debounceMs: 300,
+});
+
+void address.searchByPostalCode("1000001");
+void address.searchByAddressQuery({
+  addressQuery: "千代田",
+  pageNumber: 0,
+  rowsPerPage: 10,
+});
 ```
 
-All hooks require `dataSource` at runtime.
+## Headless Components
+
+### `PostalCodeInput`
+
+- Renders a `<form>` with `<label>`, `<input>`, and `<button>`
+- Supports controlled and uncontrolled usage
+- Calls `onSearch` with a normalized digits-only postal code
+- Defaults `inputMode="numeric"` unless overridden with `inputProps`
 
-The hook public APIs stay string-based:
+### `AddressSearchInput`
 
-- `useJapanPostalCode().search(value: string)`
-- `useJapanAddressSearch().search(query: string)`
-- `useJapanAddress().searchByPostalCode(value: string)`
-- `useJapanAddress().searchByKeyword(query: string)`
+- Renders the same minimal form structure
+- Supports controlled and uncontrolled usage
+- Calls `onSearch` with a trimmed query string
 
-Internally, the hooks build request objects before calling the data source:
+Both components accept:
 
-- postal-code lookup: `{ value, pageNumber: 0, rowsPerPage: 100 }`
-- address search: `{ freeword, pageNumber: 0, rowsPerPage: 100 }`
+- `inputProps` for the rendered `<input>`
+- `buttonProps` for the rendered `<button>`
 
-Optional request flags such as `includeCityDetails` and
-`includePrefectureDetails` are omitted unless your own data source
-implementation sets them explicitly.
+## Data Source Integration
 
-## Error Handling Notes
+The package exports types for both sides of the integration:
 
-`JapanAddressDataSource` should return `Page<JapanAddress>` directly from both
-methods. Hooks preserve that page payload as-is, so consumers can read
-`data.elements`, `data.totalElements`, `data.pageNumber`, and
-`data.rowsPerPage` directly.
+- `JapanAddressDataSource`
+- `JapanPostSearchcodeRequest`
+- `JapanPostAddresszipRequest`
+- `JapanPostalCodeSearchInput`
+- `JapanAddressSearchInput`
+- `JapanAddressRequestOptions`
 
-Both methods may also receive an optional second argument:
+The optional second argument to each data-source method is:
 
 ```ts
 type JapanAddressRequestOptions = {
@@ -252,63 +302,29 @@ type JapanAddressRequestOptions = {
 };
 ```
 
-Hooks pass `signal` so your data source can cancel superseded requests,
-`reset()` calls, and unmount cleanup when your backend layer supports aborts.
-
-Recommended error-code mapping:
-
-| Situation | Recommended code |
-| --- | --- |
-| Invalid postal code input | `invalid_postal_code` |
-| Blank keyword input in hook-side pre-validation | `invalid_query` |
-| Network failure | `network_error` |
-| Request aborted / timeout | `timeout` |
-| No matching addresses on backends that surface misses as errors | `not_found` |
-| Malformed success payload | `bad_response` |
-| Other backend failures | `data_source_error` |
-
-In this repository's reference demo flow, the sample `dataSource` classifies
-failed requests by HTTP status code only. Current beta-compatible flows may
-return `200` with an empty page for both blank `addresszip` requests and
-postal-code misses, and those should stay successful page results. Other
-`400` responses can still map to `invalid_query`, `404` remains useful for
-backends that intentionally surface misses as errors, and `504` maps to
-`timeout`.
-
-## Headless Components
-
-`PostalCodeInput` and `AddressSearchInput` provide behavior and DOM structure
-without bundled styles, so you can plug them into your own design system.
-
-Both components also support native prop passthrough:
-
-- `inputProps`: forwarded to the rendered `<input />`
-- `buttonProps`: forwarded to the rendered `<button />`
-
-Use these for `id`, `name`, `placeholder`, `aria-*`, `autoComplete`,
-`className`, and form integration. `PostalCodeInput` defaults to
-`inputMode="numeric"` unless you override it through `inputProps`.
-
-## Data Source and Server Integration
+The hooks pass `signal` so your data source can cancel superseded requests,
+`cancel()` calls, `reset()` calls, and unmount cleanup.
 
-Use this package with your own backend server. The official Japan Post flow
-uses token-based authentication, so browser apps should not hold upstream
-credentials directly. The supported integration model is a real server-backed
-flow.
+This repository's reference backend uses these routes:
 
-This repository includes `apps/minimal-api` as the reference local server. It
-wraps Japan Post API ver 2.0 and is intended for local development and
-integration testing. The demo's `/minimal-api` path is only a development-time
-route to that local server. When the upstream payload includes both structured
-address parts and a free-form `address` string, the reference server keeps the
-display address non-duplicated instead of concatenating both blindly.
+- `POST /q/japanpost/searchcode`
+- `POST /q/japanpost/addresszip`
 
-Timeout messages can differ depending on whether the token exchange timed out or
-the upstream lookup request timed out. Both cases still map cleanly to the
-`timeout` error code.
+But those route names are not part of the package API. They are just the
+example used by `apps/demo` and `apps/minimal-api`.
 
-## SSR
+## Constraints And Notes
 
-Use your server-side API from the `dataSource` implementation, and keep token
-exchange plus upstream signing on the server. React hooks and UI components
-should stay in client components.
+- `dataSource` is required at runtime for all hooks.
+- `isValidJapanPostalCode()` checks for an exact 7-digit postal code after
+  normalization. `useJapanPostalCode()` is less strict and accepts `3-7`
+  digits for prefix lookup.
+- `formatJapanPostalCode()` inserts a hyphen only when the normalized value is
+  exactly 7 digits.
+- `cancel()` on `useJapanPostalCode()` and `useJapanAddressSearch()` aborts the
+  in-flight request but keeps the latest settled `data` and `error`.
+- `reset()` clears both `data` and `error`.
+- The package does not require a backend to return `404` for misses. Returning
+  `200` with an empty page is also compatible with the hook contract.
+- Use your own server-side API in the `dataSource` implementation. Keep Japan
+  Post credentials and token exchange on the server side.

package/dist/index.d.ts

@@ -1,11 +1 @@
-export { AddressSearchInput } from './components/AddressSearchInput';
-export { PostalCodeInput } from './components/PostalCodeInput';
-export { createJapanAddressError } from './core/errors';
-export { formatJapanPostalCode, normalizeJapanPostalCode, } from './core/formatters';
-export { normalizeJapanPostAddressRecord } from './core/normalizers';
-export type { AddressSearchInputProps, JapanAddress, JapanAddressDataSource, JapanAddressError, JapanAddressErrorCode, JapanPostAddresszipRequest, JapanPostSearchcodeRequest, JapanAddressRequestOptions, JapanAddressSearchResult, JapanPostalCodeLookupResult, NormalizedJapanAddressRecord, Page, PostalCodeInputProps, UseJapanAddressOptions, UseJapanAddressResult, UseJapanAddressSearchOptions, UseJapanAddressSearchResult, UseJapanPostalCodeOptions, UseJapanPostalCodeResult, } from './core/types';
-export { isValidJapanPostalCode } from './core/validators';
-export { useJapanAddress } from './react/useJapanAddress';
-export { useJapanAddressSearch } from './react/useJapanAddressSearch';
-export { useJapanPostalCode } from './react/useJapanPostalCode';
-//# sourceMappingURL=index.d.ts.map
+export {}