Debian Patches

Status for node-lucide/1.72.0+dfsg+~cs5.3.0-1

Patch Description Author Forwarded Bugs Origin Last update
rollup-plugins-esbuild.patch Build rollup projects with Debian's esbuild Debian ships esbuild itself (/usr/share/nodejs/esbuild) but not
rollup-plugin-esbuild, rollup-plugin-summary nor rollup-plugin-visualizer.
.
This patch replaces rollup-plugin-esbuild with a small transform-only plugin
built on esbuild's `transform` API, and drops the summary/visualizer plugins.
Rollup keeps resolving, bundling and emitting the requested format, so a
transform hook is all that is needed.
.
It also extends nodeResolve() to relative imports: TypeScript sources use
extension-less directory imports ('./icons' -> './icons/index.ts'), which
rollup cannot resolve by itself. Without it, `rollup -c` either leaves the
imports unresolved or, with rollup-plugin-typescript, crashes:
- Debug Failure. Encountered 'paths' without a 'baseUrl'... (packages/vue)
- TypeError: Cannot read properties of undefined (reading 'include')
The previous @babel/core based workaround for packages/vue is therefore
dropped, and packages/vue builds again from its own rollup.config.mjs,
including the dist/esm bundles (see rollup-preserve-modules-dfsg.patch for
the unrelated preserveModulesRoot/sanitizeFileName issue).
Andrew Lee (李健秋) <ajqlee@debian.org> with help of LLM not-needed
rollup-preserve-modules-dfsg.patch Do not sanitize chunk file names when preserving modules Rollup derives the "[name]" placeholder of preserved modules from the module
absolute path: it sanitizes that path first (sanitizeFileName), then checks
it against the resolved preserveModulesRoot. sanitizeFileName replaces "+"
with "_", so in a source tree named "node-lucide-<version>+dfsg" the
sanitized path no longer starts with preserveModulesRoot and rollup falls
back to a path relative to the input base, which is then rejected:
.
[!] RollupError: Invalid substitution
"../../node-lucide-1.70.0_dfsg/packages/vue/src/lucide-vue" for placeholder
"[name]" in "output.entryFileNames" pattern
.
Both packages/lucide and packages/vue use preserveModules with a
"[name]-based" entryFileNames, so the ESM bundles cannot be built at all
from a "+dfsg" directory.
.
Disabling sanitization is safe here: the generated names only come from icon
and module file names, which contain no character that needs sanitizing.
.
This is a packaging-specific workaround (Debian source directories are the
ones carrying a "+"); it should be dropped once upstream sets
preserveModulesRoot itself or rollup is fixed.
Jérémy Lal <kapouer@melix.org> not-needed 2026-11-06
fix-components-builds.patch Fix components builds This is needed to work around missing or renamed deps, and simplify build Jérémy Lal <kapouer@melix.org> not-needed 2026-11-06

All known versions for source package 'node-lucide'

Links