chore: self vendor boolean@3.2.0#7011
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
This comment has been minimized.
This comment has been minimized.
| @@ -0,0 +1,19 @@ | |||
| const boolean = function (value: any): boolean { | |||
There was a problem hiding this comment.
context:
./vendor/boolean/build/lib is needed such that we do not require an extra build step.
./vendor/boolean/lib could be removed.
including both is common
There was a problem hiding this comment.
please remove vendor/boolean/lib to tighten the diff
| "global-agent": "^3.0.0" | ||
| } | ||
| }, | ||
| "overrides": { |
There was a problem hiding this comment.
both are needed to create a package that does not contain the warning when ran with npm 12.
|
The vendored TS is not really needed IMO. Please just keep JS + metadata + license. |
32d9ba0 to
0efd62c
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
robertolopezlopez
left a comment
There was a problem hiding this comment.
if it is just about vendoring one package, it seems good
| declare const isBooleanable: (value: any) => boolean; | ||
| export { isBooleanable }; |
There was a problem hiding this comment.
do we need these .ts files?
There was a problem hiding this comment.
It can successfully pack without them. I removed them.
0efd62c to
6b17a6a
Compare
This comment has been minimized.
This comment has been minimized.
6b17a6a to
879dd0d
Compare
This comment has been minimized.
This comment has been minimized.
879dd0d to
eac323a
Compare
PR Reviewer Guide 🔍
|
Pull Request Submission Checklist
are release-note ready, emphasizing
what was changed, not how.
What does this PR do?
This PR aims to remove the deprecation warning when installing the CLI from npm.
Bundles boolean, and by extension roarr, and global-agent.
Where should the reviewer start?
Test current behaviour.
How should this be manually tested?
What's the product update that needs to be communicated to CLI users?
Nothing.
What are the relevant tickets?
CLI-1417