Skip to content

Releases: vanjs-org/mini-van

0.5.6: no escaping for text inside <script> tag

10 Mar 06:21
Compare
Choose a tag to compare
0.5.6: no escaping for text inside <script> tag

0.5.5: Fix the minor type issue of van.state in mini-van.d.ts, van-plate.d.ts and shared.d.ts

09 Mar 00:10
Compare
Choose a tag to compare

0.5.4: API update to match VanJS's API simplification in 1.4.0

08 Mar 17:19
Compare
Choose a tag to compare

API update to match VanJS's API simplification in 1.4.0: vanjs-org/van#280.

`mini-van.d.ts` improvement

31 Oct 04:28
Compare
Choose a tag to compare

Allow Node (thus DocumentFragment) type as parameters of tag functions.

0.5.2: type simplification

19 Oct 23:55
Compare
Choose a tag to compare
  • Simplify the definition for BrowserTags with the help of HTMLElementTagNameMap.
  • Tag functions should be readonly properties.

0.5.1 was skipped due to faulty NPM release.

0.5.0: Optimize van-plate mode to reduce string concatenations in deeply nested HTML

25 Sep 22:54
Compare
Choose a tag to compare

A ~10% performance improvement was observed for webpages with typical complexity. See the benchmark result for details.

0.4.2: Update `mini-van.d.ts` in a way similar to VanJS `1.2.1` release

20 Sep 03:12
Compare
Choose a tag to compare

Update mini-van.d.ts in a way similar to VanJS 1.2.1 release.

Version 0.4.1 is skipped due to the faulty release of Deno module.

0.4.0: Enabling fullstack rendering

07 Sep 22:51
Compare
Choose a tag to compare
  • Provide the implementation for all the states and state binding related API (van.state, van.derive, van._, van.val, van.oldVal, state-valued property, state-derived property, state-valued child node, state-derived child node) with the absence of reactivity. This is crucial for cross-platform UI components to work on both VanJS (client-side) and Mini-Van (server-side).
  • Change the behavior of assigning props values in tag functions. From 0.4.0, we will consistently assign the property values via setAttribute in Mini-Van. This is because for SSR (server-side rendering), which is Mini-Van's primary use case, setting the properties of a DOM node won't be visible in the rendered HTML string unless the action of setting the property itself will also set the corresponding HTML attribute (e.g.: setting the id property of a DOM node will also set the id attribute). This is helpful as input({type: "text", value: "value"})`` can be rendered as in **Mini-Van**0.4.0but would be rendered as`` if we set the property value via DOM property.
  • Define types for cross-platform (SSR and CSR) UI components to use without any dependencies on concrete types from Mini-Van or VanJS.
  • Simplify some type definition with the help of builtin type Record.

0.3.9: Support readonly properties of DOM elements

16 Jul 05:49
Compare
Choose a tag to compare

0.3.8: Use function `Element.append` to further reduce the bundle size

22 Jun 05:48
Compare
Choose a tag to compare
0.3.8: Use function `Element.append` to further reduce the bundle size