tsimp

TSimp

pronounced as T Simp, read as TS imp

Just like SpuckJs, but better and typed!

Description:

1. Object oriented, every TSimp object converts to DOM element
2. Autocompletion and JS-Doc documentation included, thnx to Typescript
3. State Management
4. Effect Management
5. An easy and intuitive way of sharing states

Features

You can read this to get an idea of getting started, these are spuckjs docs but both the libraries are very similar.
You can't edit css in this library like you did in SpuckJs, it is recomended to use Tailwind.
You'll be using a build tool and Vite is recomended.

Initializing:

npm create vite@latest
npm i
npm i tsimp

main.ts

import TSimp from 'tsimp';

const element = new TSimp({ type: 'h1', parent: '#app', class: "heading", id: "head" });
element.prop = { text: "Hello World" };
element.attr = { title: "Heading" };
element.make();

DOM Methods

Library gives some methods to manipulate and listen to the dom.
render(): converts/update a virtual element (JSimp object) into a physical DOM element.
mount() : puts the element to the dom.
unMount(): removes the element from the dom.
isMount(): checks if the element is in the dom.
onMount(func): calls the func function when an element is mounted.
onUnmount(func): ...element is unmounted.

States

States are internal variables of elements that when change automatically update their references in these specific properties:
html, text, css, value, class, id.

const [count, setCount] = element.state('count', 0);
element.prop = { text: "count is $count$" }

$statename$ - This textual way of referencing states is used in the mentioned 6 properties to get a truly reactive nature.
count is a function that returns the state value and can be used inside effects and events to get the latest value of thr state. setCount updates the state value.

const button = new TSimp({ type: 'button', parent: '#app' });
button.prop = { text: 'Update Count' };
button.events = {
  click: () => setCount(count() + 1)
}
button.make();

count() in the event will always have the latest value of the state as that line of code will call the getter function again.

Sharing States

Suppose another element wants to show the count of element in its text. For that, it will subscribe for element's state to access them.

const para = new TSimp({ type: 'p', parent: '#app' });
para.subscribe(element, []);
para.prop = { text: "Element's count is %count% };
para.make();

para subscribed to the element for all its states.
[] => all states.
['count', 'color'] => subscribing to specific states.

After subscribing, the count state of the element became the pseudoState of para, and these states are referenced like this:
%stateName%.

Subscription Events:

_.onSubscribed(func): Called on the subscriber element when subscription is added.
_.onnewSubscriber(func): Called on the element to which the subscriber is subscribing when subscription is added.

Effects:

Effects are functions that get called when some states or pseudoStates (dependencies) change

@param func — this function will get called when the dependencies change

@param dependencyArray — add states that will affect the effect, examples:

['$count$', '%color%'] (this will run the effect when either of state/pseudoState changes)
['f'] (this will run the effect on the first render only)
['e'] (this will run the effect on every render)

@param onFirst — default: true, by default every effect runs on its first render whether the deps change or not.

element.effect(func, dependencyArray, onFirst=true);

para example:

para.effect(() => {
  console.log('Effect Ran')
}, ['%count%']);