Props are no longer rememebered between renders. For instance, rendering <input checked /> and then <input /> will not cause the checked prop to be deleted on the actual element.
The internal Renderer API has been changed to use inheritance and away from the intrinsic generator API.
Renderer.prototype.render and Context.prototype.refresh now return rendered values rather than undefined.
The library is no longer transpiled.
The esm directory in the package has been deleted. Refer to index, dom and html in the root of the package instead.
Some types have been simplified
- Tag no longer takes a type parameter.
- The types Props, FunctionComponent, GeneratorComponent, IntrinsicProps, ChildIterator, ChildGenerator and Key have been removed from the public API.

Added

UMD build.
crank-ref props.
Context.prototype.schedule.
Context.prototype.cleanup.
Context.prototype.props.
Context.prototype.value.
dispatchEvent now does bubbling and capturing correctly.

Fixed

Performance improvements in terms of execution time, runtime memory costs, and library size.
Fixed Context.prototype.dispatchEvent not responding to stopPropagation and stopImmediatePropagation.
Fixed nested SVG elements not rendering SVGElements in some cases.
Improved error handling.

Readme

Source

Astro Crank

An integration for Crank in Astro

Installation

npm i astro-crank

Add the integration to astro.config.mjs.

import {defineConfig} from "astro/config";
import crank from "astro-crank";

export default defineConfig({
  // ...
  integrations: [crank()],
});

Keywords

FAQs

What is astro-crank?

Is astro-crank well maintained?

Last updated on 26 Apr 2024

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install