dphelper 4.3.5 → 4.5.2

package/README.md

@@ -37,7 +37,7 @@
 
 ## About
 
-**dphelper** is a powerful, zero-dependency utility library that brings together **303 production-ready tools** for web developers, AI engineers, and DevTools creators.
+**dphelper** is a powerful, zero-dependency utility library that brings together **production-ready tools** for web developers, AI engineers, and DevTools creators.
 
 Think of it as your **universal toolbox** - from DOM manipulation to cryptographic operations, from real-time WebSocket handling to AI-powered token optimization. No more juggling multiple packages. One import, infinite possibilities.
 
@@ -87,6 +87,43 @@ Import it precisely **once** in your entry point (e.g., `index.js`, `main.ts`, o
 import "dphelper";
 ```
 
+### Modular imports
+
+For a smaller bundle or cleaner tree-shaking, import only the tool you need. Each modular entry point exposes the tool both as a **named export** and on the **global `dphelper`** object, so existing global-usage code keeps working unchanged.
+
+```ts
+import { sanitize } from "dphelper/sanitize"
+import { format } from "dphelper/format"
+import { fetch } from "dphelper/fetch"
+import { security } from "dphelper/security"
+
+sanitize.html("<strong>safe text</strong>")
+format.currency(1234.56, "en-US", "USD")
+await fetch.get("https://api.example.com")
+security.ulid()
+```
+
+The same tool is also available on the global after import:
+
+```ts
+import "dphelper/format"
+
+// Identical to the named export above
+dphelper.format.currency(1234.56, "en-US", "USD")
+```
+
+> [!NOTE]
+> Every tool under `tools/` is published as `dphelper/<tool>` (e.g. `dphelper/array`, `dphelper/i18n`, `dphelper/worker`). The full list is generated automatically from the `tools/` directory at build time, so adding a new tool creates its modular entry point with no extra configuration.
+
+> [!IMPORTANT]
+> **TypeScript + `resolvePackageJsonExports`:** Modular subpath imports (e.g. `import { sanitize } from "dphelper/sanitize"`) are resolved through the `exports` map in `dphelper`'s `package.json`. If your `tsconfig.json` sets `"resolvePackageJsonExports": false`, TypeScript will fall back to physical path resolution and fail with `Cannot find module 'dphelper/<tool>' or its corresponding type declarations` (TS2307), because the tool actually lives under `modules/<tool>` rather than at the package root.
+>
+> To fix it, either:
+> - keep `"resolvePackageJsonExports": true` (the default for `moduleResolution: "bundler"`), or
+> - import from the physical path: `import { sanitize } from "dphelper/modules/sanitize"`.
+>
+> Note: this is a TypeScript-only resolution issue. Vite and other bundlers resolve the subpath correctly at build/runtime via the `exports` map regardless of that flag.
+
 For plain HTML/CDN:
 
 ```html
@@ -95,7 +132,7 @@ For plain HTML/CDN:
 <!-- Optional check -->
 <script>
   console.debug(dphelper.version);  // latest version
-  console.debud(dphelper.isBrowser); // true
+  console.debug(dphelper.isBrowser); // true
 </script>
 ```
 
@@ -148,33 +185,6 @@ dphelper.i18n.number(1234.56, 'de-DE', { style: 'currency', currency: 'EUR' });
 // Relative time
 dphelper.i18n.relativeTime(Date.now() - 3600000); // "1 hour ago"
 ```
-
----
-
-## 🖼️ Image Module
-
-```javascript
-// Load image
-const img = await dphelper.image.load('photo.jpg');
-
-// Resize
-const resized = dphelper.image.resize(img, 100, 100);
-
-// Crop
-const cropped = dphelper.image.crop(img, { x: 0, y: 0, width: 50, height: 50 });
-
-// Apply filters
-const filtered = dphelper.image.filter(img, { brightness: 1.2, sepia: 0.5 });
-
-// Rotate/Flip
-const rotated = dphelper.image.rotate(img, 90);
-const flipped = dphelper.image.flip(img, 'horizontal');
-
-// Grayscale/Blur
-const gray = dphelper.image.grayscale(img);
-const blurred = dphelper.image.blur(img, 5);
-```
-
 ---
 
 ## 🗜️ Compression Module

package/SECURITY.md

@@ -1,27 +1,27 @@
-# Security Policy
-
-## Supported Versions
-
-| Version | Supported |
-| ------- | --------- |
-| 3.9.x   | ✅        |
-| < 3.5   | ❌        |
-
-## Security Standards
-
-- **NIST SP 800-53:** 98% compliance
-- **OWASP Top 10:** 100% compliance
-- **Socket.dev:** 90%+ target
-
-## Reporting a Vulnerability
-
-Email: architecture@biglogic.ca
-Response: Within 24 hours
-
-## Security Features
-
-- PBKDF2 310k iterations (OWASP 2023)
-- AES-GCM 256-bit encryption
-- TLS 1.2+ enforcement
-- WebSocket wss:// only
+# Security Policy
+
+## Supported Versions
+
+| Version | Supported |
+| ------- | --------- |
+| 3.9.x   | ✅        |
+| < 3.5   | ❌        |
+
+## Security Standards
+
+- **NIST SP 800-53:** 98% compliance
+- **OWASP Top 10:** 100% compliance
+- **Socket.dev:** 90%+ target
+
+## Reporting a Vulnerability
+
+Email: architecture@biglogic.ca
+Response: Within 24 hours
+
+## Security Features
+
+- PBKDF2 310k iterations (OWASP 2023)
+- AES-GCM 256-bit encryption
+- TLS 1.2+ enforcement
+- WebSocket wss:// only
 - Input validation on all endpoints