It should be PicoMPA, instead i named my tiny #progressive #enhancement tools/lib #PicoSPA.
It provides the small functions I use day in and day out on various sites to make an #MPA feel more like an app (or an #SPA).

The latest addition is: nothing.

It is just the smallest polyfill for the `navigate` event, that is loaded when needed, since not all browsers support it.
https://picossg.dev/tools/picospa/navigation.html 👈🏻

`navigation.addEventListener('navigate', ...`
read ☝️ how to pimp an MPA with it.

#useThePlatform

May I show you my build process?
The npm script to build my JS files into one:

"build": "cat src/*.js > _dist/picospa.js",

Once this gets `npm deploy`ed the CDN minifies it and provides a *.min.js

for example for
#picoSPA https://picossg.dev/tools/picospa/ the JS file is at
https://cdn.jsdelivr.net/npm/@pic0/spa@2.1.0/_dist/picospa.min.js

https://codeberg.org/wolframkriesing/picospa/src/branch/main/package.json#L22

Say hello to #picoSPA. (used to be named #SPAish, but that name was uuuh).

https://picossg.dev/tools/picospa/

PicoSPA is a progressive enhancement toolkit, made of a few small functionalities to make a site more interactive and modern without the need to use a full #SPA framework. It is not a framework, it is a set of tools to enhance your #MPA.

Seems like I am building a `pico`-series :)
https://picossg.dev the #SSG and now the #SPA tool PicoSPA.

#useThePlatform #minimal #web