cms-renderer 0.6.6 → 0.6.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -147,7 +147,7 @@ NEXT_PUBLIC_CMS_API_URL=https://cms.example.com
147
147
 
148
148
  Use `CMS_API_KEY` when your CMS requires authenticated access.
149
149
 
150
- `NEXT_PUBLIC_CMS_API_URL` is only used by the default `component` export from `cms-renderer/lib/schema`. If you call `configureSchema(...)` directly, pass `cmsUrl` explicitly instead.
150
+ The default `schema` / `component` exports from `cms-renderer/lib/schema` read `NEXT_PUBLIC_CMS_API_URL` on **first use** (lazy), not when the module loads — so importing only `configureSchema` never touches that env. If you call `configureSchema(...)` directly, pass `cmsUrl` explicitly instead.
151
151
 
152
152
  If no website ID is available, `ParametricRoutePage` throws at runtime.
153
153
 
@@ -206,7 +206,7 @@ Available methods:
206
206
  - `fetchSingleById(id)`
207
207
  - `translation(language)`
208
208
 
209
- If you use the default `component` export, it reads `NEXT_PUBLIC_CMS_API_URL` from the environment. If you call `configureSchema(...)` directly, pass the CMS origin/base URL as `cmsUrl`.
209
+ If you use the default `component` export, it reads `NEXT_PUBLIC_CMS_API_URL` from the environment on first access. If you call `configureSchema(...)` directly, pass the CMS origin/base URL as `cmsUrl`.
210
210
 
211
211
  ## Custom Component Code Generation
212
212