Timeline for How can I forcibly exclude a nested dependency for NPM?
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 28 at 10:10 | comment | added | ceztko |
This seems to work better for me than the other strategy but the package could have been named better, such as dummy-dependency or something like that. dry-uninstall naming doesn't really grasp the point of the package, IMO. Anyway, there should be official support for this future (hence a RFE should be done to NodeJs), so there's no need for workarounds like this that can break inadvertently.
|
|
| S Aug 30, 2023 at 10:39 | review | First answers | |||
| Sep 1, 2023 at 10:53 | |||||
| S Aug 30, 2023 at 10:39 | history | answered | Denys Potapov | CC BY-SA 4.0 |