@virtual-content/core 0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 eykettle
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,39 @@
+# @virtual-content/core
+
+Framework-independent virtual content engine package.
+
+This package provides the core virtualizer, geometry helpers, layout engines, range calculation,
+anchor correction, and shared types.
+
+The current public line is `0.1.x`. The package is usable, but the API is still pre-1.0 and may
+receive small contract adjustments before `1.0.0`.
+
+## Install
+
+```bash
+pnpm add @virtual-content/core
+```
+
+## Entry Point
+
+```ts
+import { Virtualizer, createRect } from "@virtual-content/core";
+import type { VirtualContentOptions } from "@virtual-content/core";
+```
+
+Use this package directly when building a framework adapter, a custom renderer, or non-DOM virtual
+content logic. Solid applications should usually install `@virtual-content/solid` instead.
+
+Current layout engines:
+
+- `LinearBandEngine` for `linear` and current `grid` layouts.
+- `SpatialRectEngine` for `masonry` and `free` layouts.
+
+Current `grid` support is band virtualization. The public layout API keeps `lanes` and
+`gap.cross` as target grid design fields, but item-level lane placement is not implemented yet.
+For spatial layouts, `range.maxItems` is the implemented materialization cap; `range.maxPx` is
+currently limited to linear and grid band ranges.
+
+The beta layout contract treats `layout.gap` as virtual item or band spacing and
+`layout.padding` as scrollable content canvas inset. These values belong in core geometry rather
+than adapter CSS so range calculation, scroll targets, total size, and anchor correction agree.