node-prune

Issue description by Claude Summary The flag in node-prune only matches against the base filename/directory name () rather than the full path, making it impossible to exclude files or directories within specific node modules. Current Behavior When using the flag with glob patterns, the pattern is only matched against the filename or directory name, not the full path relative to the target directory. Source Code Reference:** Expected Behavior The exclude patterns should be able to match against the full relative path, allowing for more granular control over what gets excluded. Use Case Example When trying to preserve image assets in a specific package while still allowing pruning of images elsewhere: Problem Scenarios Scenario 1: Package-specific exclusions Scenario 2: Path-specific exclusions Current Workaround The only current workaround is to exclude the entire filename/directory name globally: This is too broad and prevents legitimate pruning in other locations. Proposed Solution Modify the exception matching logic to support both filename patterns and path-based patterns: Alternative Solution Add a separate flag that specifically matches against full paths, keeping the current behavior for backward compatibility.

Something happen and you can no longer get this package from GH, it gives you a 503. `

Currently fails on 32bit Raspberry PI / also in linux/arm Docker containers: I found that using "arch=arm" does work, but this workaround is a bit ugly in Dockerfiles: