Speaking of which:
I made the executive decision to work on `baseline` today. Still no package release but getting closer, I promise!
Today was some codebase work, local repo is clean and pushed. I'll let my mood decide tonight what the next open loop is.
Repo link:
https://github.com/apleasantview/eleventy-plugin-baseline/commits/main/
I've just released a package update on npm for `eleventy-plugin-baseline`!
I've been doing some vision work on the plugin since a bit, which also includes documentation changes but I thought "Let's not wait and just release something".
I'll sum up the changes included in this one in a minute.
https://www.npmjs.com/package/@apleasantview/eleventy-plugin-baseline
An experimental Swiss army knife toolkit for Eleventy. Latest version: 0.1.0-next.32, last published: 16 minutes ago. Start using @apleasantview/eleventy-plugin-baseline in your project by running `npm i @apleasantview/eleventy-plugin-baseline`. There are no other projects in the npm registry using @apleasantview/eleventy-plugin-baseline.
The assets pipeline got a full refactor, esbuild and postcss modules are now pure processing functions, wired through a single assets-core plugin.
Image shortcode tightened up: content-hash filenames to prevent collisions, alt validation warns instead of crashing, transformOnRequest retry scoped to dev mode only.
x-default hreflang lands in sitemaps.
Dead code swept across 7 files. Every JS file in the plugin now has proper documentation.
25 files changed, 633 insertions, 533 deletions.
Cris.