hazo_config 2.1.6 → 2.1.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/CHANGE_LOG.md CHANGED
@@ -1,5 +1,10 @@
1
1
  # Changelog
2
2
 
3
+ ## 2.1.7 — 2026-05-30
4
+
5
+ ### Fixed (bundling defect surfaced by seo_monitor)
6
+ - Removed `import 'server-only';` from `src/server/index.ts`. Next 15's "Collecting page data" build phase evaluates `route.ts` modules without setting the `react-server` resolution condition, so the marker throws and breaks `next build` for every legitimate server-side consumer (e.g. `hazo_notify/adapters/telegram` pulls `hazo_config/server` for INI parsing, which then loads in seo_monitor's telegram route at build time). Documented the deliberate omission in the file. `HazoConfig` uses `fs`/`path`, so a real Client Component import still fails at runtime — we just lose fail-fast at module load. Same root cause as hazo_logs@2.0.2 and hazo_api@2.1.1.
7
+
3
8
  ## 2.1.6 — 2026-05-29
4
9
 
5
10
  ### Changed (internal — no API surface change)
@@ -4,10 +4,17 @@
4
4
  * This entry point contains Node.js-specific code that uses fs and path modules.
5
5
  * It should only be imported in server-side code (API routes, server components, etc.)
6
6
  *
7
+ * We intentionally do NOT `import 'server-only'` here because Next 15's
8
+ * "Collecting page data" build phase evaluates route.ts modules without the
9
+ * `react-server` resolution condition, so the marker throws and breaks
10
+ * `next build` for every legitimate server-side consumer. HazoConfig uses
11
+ * fs/path, so a real Client Component import still fails at runtime — we
12
+ * just lose fail-fast at module load. Same root cause as hazo_logs@2.0.2 /
13
+ * hazo_api@2.1.1.
14
+ *
7
15
  * Usage:
8
16
  * import { HazoConfig } from 'hazo_config/server'
9
17
  */
10
- import 'server-only';
11
18
  export { HazoConfig } from '../lib/config_loader.js';
12
19
  export type { HazoConfigOptions } from '../lib/types.js';
13
20
  //# sourceMappingURL=index.d.ts.map
@@ -1 +1 @@
1
- {"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/server/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAEH,OAAO,aAAa,CAAA;AAEpB,OAAO,EAAE,UAAU,EAAE,MAAM,yBAAyB,CAAA;AACpD,YAAY,EAAE,iBAAiB,EAAE,MAAM,iBAAiB,CAAA"}
1
+ {"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/server/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AAEH,OAAO,EAAE,UAAU,EAAE,MAAM,yBAAyB,CAAA;AACpD,YAAY,EAAE,iBAAiB,EAAE,MAAM,iBAAiB,CAAA"}
@@ -4,8 +4,15 @@
4
4
  * This entry point contains Node.js-specific code that uses fs and path modules.
5
5
  * It should only be imported in server-side code (API routes, server components, etc.)
6
6
  *
7
+ * We intentionally do NOT `import 'server-only'` here because Next 15's
8
+ * "Collecting page data" build phase evaluates route.ts modules without the
9
+ * `react-server` resolution condition, so the marker throws and breaks
10
+ * `next build` for every legitimate server-side consumer. HazoConfig uses
11
+ * fs/path, so a real Client Component import still fails at runtime — we
12
+ * just lose fail-fast at module load. Same root cause as hazo_logs@2.0.2 /
13
+ * hazo_api@2.1.1.
14
+ *
7
15
  * Usage:
8
16
  * import { HazoConfig } from 'hazo_config/server'
9
17
  */
10
- import 'server-only';
11
18
  export { HazoConfig } from '../lib/config_loader.js';
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "hazo_config",
3
- "version": "2.1.6",
3
+ "version": "2.1.7",
4
4
  "description": "Config wrapper with error handling",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -101,7 +101,7 @@
101
101
  },
102
102
  "peerDependencies": {
103
103
  "hazo_core": "^1.0.0",
104
- "hazo_ui": "^3.1.0",
104
+ "hazo_ui": "^3.1.3",
105
105
  "react": "^18.0.0 || ^19.0.0",
106
106
  "react-dom": "^18.0.0 || ^19.0.0",
107
107
  "tailwindcss": "^4.0.0"
@@ -1,8 +0,0 @@
1
- import { type ClassValue } from "clsx";
2
- /**
3
- * Merges class names using clsx and tailwind-merge
4
- * @param inputs - Class values to merge
5
- * @returns Merged class string
6
- */
7
- export declare function cn(...inputs: ClassValue[]): string;
8
- //# sourceMappingURL=utils.d.ts.map
@@ -1 +0,0 @@
1
- {"version":3,"file":"utils.d.ts","sourceRoot":"","sources":["../../src/lib/utils.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,KAAK,UAAU,EAAQ,MAAM,MAAM,CAAA;AAG5C;;;;GAIG;AACH,wBAAgB,EAAE,CAAC,GAAG,MAAM,EAAE,UAAU,EAAE,UAEzC"}
package/dist/lib/utils.js DELETED
@@ -1,12 +0,0 @@
1
- // Utility functions for the component library
2
- // Provides class name merging functionality using clsx and tailwind-merge
3
- import { clsx } from "clsx";
4
- import { twMerge } from "tailwind-merge";
5
- /**
6
- * Merges class names using clsx and tailwind-merge
7
- * @param inputs - Class values to merge
8
- * @returns Merged class string
9
- */
10
- export function cn(...inputs) {
11
- return twMerge(clsx(inputs));
12
- }