Please address the comments from this code review:

## Overall Comments
- Consider making `workerSrc` configurable (e.g., via an env or a small config helper) instead of hardcoding the npm mirror URL so that deployments can switch CDNs or self-host the worker without touching code.
- The new `ensureWorker` helper only checks `pdfjs.GlobalWorkerOptions.workerSrc`; if other worker-related global options are required in the future (e.g., different worker for SSR vs client), it might be worth centralizing all worker configuration there to avoid scattered setups.

## Individual Comments

### Comment 1
<location> `src/libs/pdfjs/index.tsx:6` </location>
<code_context>
+import type { ComponentProps } from 'react';
+import { Document as PdfDocument, Page as PdfPage, pdfjs } from 'react-pdf';
+
+const workerSrc = `https://registry.npmmirror.com/pdfjs-dist/${pdfjs.version}/files/build/pdf.worker.min.mjs`;
+
+function ensureWorker() {
</code_context>

<issue_to_address>
**suggestion:** Consider making the worker URL configurable instead of hardcoding a specific CDN/mirror.

Using a hardcoded `registry.npmmirror.com` URL tightly couples the app to a single external mirror and can cause issues with regional access, outages, or CSP-restricted environments. Please source this URL from configuration (env, runtime config, or a shared constants module) with a reasonable default so deployments can select their own hosting (e.g., self-hosted asset or preferred CDN).

Suggested implementation:

```typescript
import type { ComponentProps } from 'react';
import { Document as PdfDocument, Page as PdfPage, pdfjs } from 'react-pdf';

const DEFAULT_PDF_WORKER_SRC = `https://registry.npmmirror.com/pdfjs-dist/${pdfjs.version}/files/build/pdf.worker.min.mjs`;

/**
 * Resolve the PDF worker source URL from configuration with a sensible default.
 *
 * Prefer an environment-driven configuration so deployments can select their own
 * hosting (self-hosted assets, preferred CDN, etc.).
 */
const pdfWorkerSrc =
  // Public runtime config (e.g. Next.js) – adjust name to match your conventions if needed
  process.env.NEXT_PUBLIC_PDFJS_WORKER_URL ??
  DEFAULT_PDF_WORKER_SRC;

function ensureWorker() {
  if (!pdfjs.GlobalWorkerOptions.workerSrc) {
    pdfjs.GlobalWorkerOptions.workerSrc = pdfWorkerSrc;
  }
}

```

1. Define the environment variable (e.g. `NEXT_PUBLIC_PDFJS_WORKER_URL`) in your runtime configuration (.env or equivalent) if you want to override the default worker URL in specific environments.
2. If your project uses a different pattern for exposing public runtime config (for example, a `config` module or `publicRuntimeConfig` via Next.js), you may want to replace the `process.env.NEXT_PUBLIC_PDFJS_WORKER_URL` access with that shared configuration source instead, while keeping the same fallback to `DEFAULT_PDF_WORKER_SRC`.
</issue_to_address>

### Comment 2
<location> `src/libs/pdfjs/index.tsx:17-25` </location>
<code_context>
+export type DocumentProps = ComponentProps<typeof PdfDocument>;
+export type PageProps = ComponentProps<typeof PdfPage>;
+
+export const Document = (props: DocumentProps) => {
+  ensureWorker();
+  return <PdfDocument {...props} />;
+};
+
+
+
+
+export {Page, pdfjs} from 'react-pdf';
\ No newline at end of file
</code_context>

<issue_to_address>
**issue (bug_risk):** Page is re-exported without ensureWorker, which can break future usages that don’t go through Document.

Because `Page` is re-exported directly from `react-pdf`, it assumes callers always render it under this wrapped `Document`. If someone later imports `{ Page }` from this module and uses it elsewhere, the worker may not be initialized and PDF rendering can fail. To avoid this, export a local `Page` wrapper that calls `ensureWorker()` before delegating to `PdfPage`.
</issue_to_address>