Merged
Conversation
Contributor
Author
Member
|
You're absolutely right. Amazing finding! Thank you. |
Codecov Report
@@ Coverage Diff @@
## main #41 +/- ##
==========================================
- Coverage 82.22% 81.74% -0.48%
==========================================
Files 21 21
Lines 1035 1041 +6
==========================================
Hits 851 851
- Misses 184 190 +6
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

Until now pacquet just ran any script/shell commands by just directly passing the entire command to
Command::new. As per the std,Command::newtakes only the file/program name, and any additional args need to be provided via theargorargsmethod.Well now, i just touched it a little bit, to run
sh -cand pass the actual command/script to it. This runs without any errors now, and sometimes scripts contain env vars too. For example{ "scripts": { "test": "KEY=VALUE node index.js" } }Now it is passed as
sh -c "KEY=ENV node index.js. This seems to be how the peeps do it in pnpm. (in pn)And also pass any sort of additional args provided in the run command to the script. For example,
{ "scripts": { "test": "echo Hello" } }Current running
pacquet testandpacquet test Worldboth just prints "Hello", but pnpm passes any additional args provided to the script too. So now it prints "Hello World" when donepacquet test World