Add pm2-runtime to IGNORED_GLOBAL_BINARIES constant #915
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm proposing we add
pm2-runtime
to the list ofIGNORED_GLOBAL_BINARIES
based on this documentation which indicates thatpm2
should be installed globally inside of Docker containers and invoked using thepm2-runtime
binary.In my specific use case we have a script in our
package.json
file calledworkers:prod
which uses this binary, e.g.pm2-runtime start pm2.config.js
, which will fail theknip --include binaries
check since its not added to our package and is only necessary in our production environment.I'm curious if others have a strong feeling for or against including this entry.