matthewp

This is some docs

Something I want to test below...

const foo = 'bar';

matthewp

node_modules/

matthewp

import * as aud from 'audio-context-timers';

console.log(aud);

matthewp

main.zip: main.js package.json package-lock.json src lib node_modules
	zip -r $@ $^

clean:
	@rm -f main.zip deploy.json
.PHONY: clean

deploy.json: main.zip
	aws lambda update-function-code --function-name my-function-name --zip-file fileb://./$^ > $@

matthewp

let error1, error2;

try {
  await import('/mod.js');
} catch(err) {
  error1 = err;
}

try {
  await import('/mod.js');

matthewp

I recently tweeted out the following about the Extensible Web Manifesto.

matthewp

zig-cache

matthewp

This release adds support for a JavaScript module entry point. If you are using a bundler like webpack this will be used automatically and you do not need to make any changes.

Usage

Usage is described in the readme. In short you can import any of the primary classes like so:

import {
	Menu,
	Cart,

matthewp

out.mjs
node_modules/

matthewp

This is a huge release for Haunted, one of the biggest since the initial release. Before getting into features I want to give some appreciate to @jdin, @Gladear, and @chase-moskal who all made tremendous contributions to this release. That cannot go overstated, I did only a small part of this release, the Haunted community is what keeps this project alive. ❤️ 🎃 . Now that the sappy stuff is complete, on to the features!

State API

At its core Haunted is a container for state and lifecycle callbacks that is derived from hooks like useState, useMemo, even useEffect. With the component() API you get more than just that, you also get a scheduler that handles rendering and committing the result.

A lot of people have wanted to use hooks outside of the context of Haunted components. One example is using hooks inside of a LitElement component. The new State API enables this, by exposing the low-level part of Haunted which is its state container.