- #93
- #92
- #91
- #90
- #89
- #88
- #87
- #86
- #85
- #84
- #83
- #82
How to Directly Modify Project Dependency Package Source Code (node_modules)?
During development, there are times when the packages being used have some bugs or features that need to be added, and there isn’t enough time to slowly submit requests and wait for package updates. In such situations, the usual approach is to fork the package, rewrite it, and then modify the dependency source.
I always thought that forking and rewriting my own package was the only proper way to go, until I accidentally stumbled upon patch-package and, after reading the documentation carefully, discovered that pnpm and yarn2+ have long supported the ability to modify the source code of dependency packages.
pnpm has some good documentation and video examples describing how to patch specific packages. In simple terms, it creates a patches folder to store the modified packages and references the modified packages through patchedDependencies, which is a more elegant way to manage temporary fixes to packages.
You can also take a look at pnpm-patch-i.
- #81
- #80
- #79
- #78
- #77
- #76
- #75
- #74
- #73
- #72
- #71
- #70
- #69
- #68
- #67
- #66
- #65
- #64
- #63
- #62
- #61
- #60
- #59
- #58
- #57
- #56
- #55
- #54
- #53
- #52
- #51
- #50
- #49
- #48
- #47
- #46
- #45
- #44
- #43
- #42
- #41
- #40
- #39
- #38
- #37
- #36
- #35
- #34
- #33
- #32
- #31
- #30
- #29
- #28
- #27
- #26
- #25
- #24
- #23
- #22
- #21
- #20
- #19
- #18
- #17
- #16
- #15
- #14
- #13
- #12
- #11
- #10
- #9
- #8
- #7
- #6
- #5
- #4
- #3
- #2
- #1