Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking: stabilization of "patch" feature #25110

Open
5 tasks
dsherret opened this issue Aug 20, 2024 · 3 comments
Open
5 tasks

Tracking: stabilization of "patch" feature #25110

dsherret opened this issue Aug 20, 2024 · 3 comments
Labels
feat new feature (which has been agreed to/accepted)

Comments

@dsherret
Copy link
Member

dsherret commented Aug 20, 2024

// deno.json
{
  "patch": [
    "../some-package-or-workspace"
  ]
}

#25068

Questions:

  • Is "patch" an ok name? Isn't it confusing with the idea of "patching a package" where you modify a package in the vendor or node_modules directory? What better alternatives are there?
  • Can this work with git repositories? How does that work?
  • What about patching to a remote specifier?

To implement:

@lucacasonato lucacasonato added the feat new feature (which has been agreed to/accepted) label Aug 22, 2024
@lucacasonato
Copy link
Member

I think patch is a reasonable name.

@Hajime-san
Copy link
Contributor

Hi, I created a minimal example for the current patch feature.
If you find any mistakes, please let me know.

@birkskyum
Copy link
Contributor

birkskyum commented Oct 29, 2024

does this do something similar to pnpm patch https://pnpm.io/cli/patch? because then patch is a great name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat new feature (which has been agreed to/accepted)
Projects
None yet
Development

No branches or pull requests

4 participants