@effectweb/lucide 0.4.0 → 0.5.1

package/README.md

@@ -16,7 +16,9 @@ export const Toolbar = view<{ busy: boolean }, never>((model, _send) => (
 ));
 ```
 
-Named imports such as `import { Camera } from '@effectweb/lucide'` are tree-shaken in production builds. Prefer the per-icon paths above for development: prebundling the root entry preserves the full catalogue's exports and source maps. Do not force the whole catalogue into Vite's `optimizeDeps.include` for a fixed icon set. Upstream aliases, including `AlarmCheck` / `AlarmClockCheck`, and `Icon`-suffixed named exports share the same view identity. Per-icon and lazy imports also support aliases. `LucideIcon` and `LucideProps` are exported types.
+The package intentionally has **no root entry or icon barrel**. `import { Camera } from '@effectweb/lucide'` fails package resolution and TypeScript checking. Use the direct icon paths above: development servers load only the selected icons, without relying on production tree-shaking. Aliases such as `alarm-check` and `alarm-clock-check` share the same view identity.
+
+Import shared types with `import type { LucideIcon, LucideProps } from '@effectweb/lucide/types'`.
 
 ## Props
 
@@ -42,7 +44,7 @@ const load = loadIcon(name); // Effect<LucideIcon, IconLoadError>
 
 Run the Effect in an existing task/resource lifecycle and use the returned view. Module imports cache the view without creating DOM. `IconLoadError` carries `iconName` and the original `cause`; invalid untyped names also fail in the Effect error channel. Interrupting the Effect stops waiting, but cannot abort a browser module download.
 
-This entry also exports `iconNames`, the `IconName` union, and `dynamicIconImports`, a low-level Promise-based module map. Importing the registry makes the full catalogue available as lazy chunks. Prefer named imports, per-icon imports, or a small application-owned import map for a fixed set of icons. The registry is absent from ordinary icon bundles.
+This entry also exports `iconNames`, the `IconName` union, and `dynamicIconImports`, a low-level Promise-based module map. Importing the registry makes the full catalogue available as lazy chunks. Prefer per-icon imports or a small application-owned import map for a fixed set of icons. The registry is absent from ordinary icon bundles.
 
 ## Raw SVG and data
 

package/dist/types.d.ts

@@ -0,0 +1 @@
+export type { LucideIcon, LucideProps } from './attributes.js';

package/dist/types.js

@@ -0,0 +1 @@
+export {};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@effectweb/lucide",
-  "version": "0.4.0",
+  "version": "0.5.1",
   "description": "Lucide icons compiled to direct DOM views for EffectWeb",
   "homepage": "https://github.com/DerpyCrabs/EffectWeb/tree/main/packages/lucide",
   "license": "ISC",
@@ -17,10 +17,6 @@
   "type": "module",
   "sideEffects": false,
   "exports": {
-    ".": {
-      "types": "./dist/index.d.ts",
-      "import": "./dist/index.js"
-    },
     "./icons/*": {
       "types": "./dist/icons/*.d.ts",
       "import": "./dist/icons/*.js"
@@ -36,6 +32,9 @@
     "./build": {
       "types": "./dist/build.d.ts",
       "import": "./dist/build.js"
+    },
+    "./types": {
+      "types": "./dist/types.d.ts"
     }
   },
   "publishConfig": {
@@ -46,7 +45,7 @@
   },
   "peerDependencies": {
     "effect": "4.0.0-rc.112",
-    "effectweb": "^0.4.0"
+    "effectweb": "^0.5.1"
   },
   "engines": {
     "node": ">=22.14"