pnpm-patch-i

Summary When applying a patch directly from a source directory (without ), and dependency specifiers in the source previously leaked through into the patched package, leaving versions the consumer could not resolve. This PR resolves them inline: / / / `workspace:1.2.3catalog:catalog:pnpm-workspace.yamlcatalogcatalogs.npm:link:file:git+ssh:--packpnpm packyamlpnpm-workspace.yamlpnpm typecheckpnpm lintpnpm buildworkspace:catalog:--packpackage.json--packpnpm-workspace.yaml`, unknown catalog name, unrecognized protocol 🤖 Generated with Claude Code

Clear and concise description of the problem As a developer, I want to update my previous patch with new amendments. However, running always starts with the clean unpatched version and I have to reapply my past changes prior to doing the actual work. Suggested solution could accept a flag like and pre-apply the already-existing patch (and to be honest, I don't see why should this ever not used). Alternative _No response_ Additional context _No response_ Validations [x] Follow our Code of Conduct [x] Read the Contributing Guide. [x] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Description Hello @antfu , This PR replaces with a better alternative that supports both CJS and ESM. Ansis supports chained syntax for clean and readable code. Ansis is nearly as small (6.8 kB) as Picocolors (6.4 kB).