chore(deps): upgrade Lume v2.5.0 → v3.2.4 - #2
Merged
Conversation
Bumps the Lume import in deno.json to v3.2.4 (major version). Also
adds an explicit `site.add("/styles.css")` call in plugins.ts: Lume 3
no longer auto-loads CSS files for the postcss plugin, so CSS must be
registered explicitly or nothing is processed.
All other plugins in use (metas, favicon, basePath, transformImages,
simpleIcons from lume_icon_plugins, icons, prism, date, purgecss,
plaintext) remain compatible with Lume 3. `site.copy()` was
reintroduced in 3.0.1 so the static-asset copy call still works.
Deno 2.7+ satisfies the LTS 2.1 minimum, and the external
lume_icon_plugins@v0.1.1 uses only stable Lume.Site APIs (site.filter).
Verified locally: same 9 output files, with expected cosmetic
differences from updated toolchains — generator string v3.2.4,
favicon default size 48→32 (Lume 3.0.5 change), newer autoprefixer
output (drops -o- vendor prefix), and tighter Vento 2 whitespace.
Note: transform_images plugin emits a "No images to transform"
warning post-upgrade because no content actually uses it. Leaving
the plugin registered to preserve current behavior; it can be
removed as a separate cleanup if desired.
Closes #1
InfoSec: dependency upgrade to current supported major line.
No application-level security surface changes.
# Conflicts: # README.md # _site/index.html # _site/repo-readme.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
deno.jsonto v3.2.4 (major upgrade from v2.5.0).site.add("/styles.css")inplugins.ts— Lume 3'spostcssplugin no longer auto-loads CSS files.deno.lock.Plugin compatibility check
This repo uses a bigger plugin surface than eSolia.github. All of these remain compatible with Lume 3 as used here:
postcsssite.add("/styles.css")(CSS no longer auto-loaded)metas,basePath,favicon,prism,date,plaintext,purgecsstransform_imagesiconssimpleIconsfromlume_icon_plugins@v0.1.1site.filter(stable across v2→v3)site.copy([".jpg", ".webp", ".png", ".svg"])Observed output changes (local build)
Lume v2.5.0→Lume v3.2.448x48→32x32(Lume 3.0.5 change)-o-vendor prefix (updated browserslist / autoprefixer)Test plan
deno task buildproduces the same 9 output filesREADME.md/_site/InfoSec: dependency upgrade to current supported major line; reduces drift risk. No application-level security surface changes.