An npm scripts runner written in Rust.

https://github.com/egoist/dum/blob/5e37d3763363402ae4b15c91ac53d81a1e4c88ec/src/lib.rs#L37

On windows, this comparison can never be true, so rust will panic with an unhelpful message:

thread 'main' panicked at 'called `Option::unwrap()` on a `None` value' ...

Fixed version of panic message:

thread 'main' panicked at 'no package.json' ...

I often forget which scripts are available in a project if I'm using it infrequently and then have to go look inside package.json to refresh my memory.

Do you think a dum -l to list available scripts would be useful? If so happy to create a PR.

Hello,

I want to try the project, However, when I try to install via brew it fails:

❯ brew install egoist/tap/dum
==> Downloading https://github.com/egoist/dum/releases/download/v0.1.17/dum-x86_64-apple-darwin.zip
Already downloaded: /Users/user/Library/Caches/Homebrew/downloads/8e4695b0182bc89ad7024c06a32bc9c1e081158bd8bc2f996077da3b478f9a4c--dum-x86_64-apple-darwin.zip
Error: dum: SHA256 mismatch
Expected: d5bfdacc793444a35c3840b23e5716d97502360288ffee7b155a77cec019c740
  Actual: 0b2d80fbcfc8aed439c8da30a539fa390e1f9ce4f4b59926f62a457e92ff46ec
    File: /Users/user/Library/Caches/Homebrew/downloads/8e4695b0182bc89ad7024c06a32bc9c1e081158bd8bc2f996077da3b478f9a4c--dum-x86_64-apple-darwin.zip
To retry an incomplete download, remove the file above.

Hi,

I was trying out dum and noticed that there is one mistake (?) it does in how it interprets the PATH environment variable. Pasting some logs below to give a clearer picture.

$ cat file.js
Object.entries(process.env).forEach(([key, value]) => {
  if (key.startsWith("npm_")) {
    // Skip the npm related envs as those are not supported yet by `dum`.
    return;
  }
  console.log(`${key}: ${value}`);
});

The following are the results from npm and dum respectively. I'm only pasting the differences in output here.

$ npm run env
NODE: /usr/local/lib/node_modules/node/bin/node
INIT_CWD: /Users/faizaan.m/Developer/webpro-frontend
PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/faizaan.m/Developer/webpro-frontend/node_modules/.bin:/Users/faizaan.m/.cargo/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/Postgres.app/Contents/Versions/latest/bin:/Users/faizaan.m/.cargo/bin
_: /usr/local/bin/node

$ dum env
PATH: /Users/faizaan.m/.cargo/bin:/Users/faizaan.m/.cargo/bin:/Users/faizaan.m/.cargo/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/Postgres.app/Contents/Versions/latest/bin:/Users/faizaan.m/.cargo/bin:/Users/faizaan.m/Developer/webpro-frontend/node_modules/.bin
_: /usr/local/bin/node

As you can see there are a couple of differences,

1. INIT_CWD is missing from dum but this is easily fixable by adding current_dir to the envs Map.
2. NODE is missing from dum, but I think using the result of which node might fix this (or we can evaluate if this is needed)
3. PATH is different in both versions - npm injects it own internal binary into the PATH. While one could argue that this is not necessary for dum to support, there's one more bigger issue.

Let's say we start with the following PATH value

$ echo $PATH
/Users/faizaan.m/.cargo/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/Postgres.app/Contents/Versions/latest/bin

And then I change the PATH

$ export PATH=$PATH:/opt/new-tool

Then, if I rerun the above commands, this is the output I see. Again, pasting only the differences.

$ npm run env
PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/faizaan.m/Developer/webpro-frontend/node_modules/.bin:/Users/faizaan.m/.cargo/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/Postgres.app/Contents/Versions/latest/bin:/Users/faizaan.m/.cargo/bin:/opt/new-tool

$ dum env
PATH: /Users/faizaan.m/.cargo/bin:/Users/faizaan.m/.cargo/bin:/Users/faizaan.m/.cargo/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/Postgres.app/Contents/Versions/latest/bin:/Users/faizaan.m/.cargo/bin:/Users/faizaan.m/Developer/webpro-frontend/node_modules/.bin

You can see that /opt/new-tool is missing when running via dum. I believe this is because env! is injecting the value when compiling dum thereby hardcoding the value into the binary.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | FranzDiebold/github-env-vars-action | action | patch | v2.3.0 -> v2.3.1 |

Release Notes

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | FranzDiebold/github-env-vars-action | action | major | v1.3.0 -> v2.3.0 |

Release Notes

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | actions/upload-artifact | action | major | v1 -> v2 |

Release Notes

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | FranzDiebold/github-env-vars-action | action | minor | v1.2.1 -> v1.3.0 |

Release Notes

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | anyhow | dependencies | patch | 1.0.51 -> 1.0.52 |

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | actions/cache | action | patch | v2.1.6 -> v2.1.7 |

Release Notes

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

• Cargo.toml (cargo)
• .github/workflows/release.yml (github-actions)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding PR is merged
• Enable Renovate Dependency Dashboard creation
• If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
• Ignore node_modules, bower_components, vendor and various test/tests directories
• Autodetect whether to pin dependencies or maintain ranges
• Rate limit PR creation to a maximum of two per hour
• Limit to maximum 10 open PRs at any time
• Group known monorepo packages together
• Use curated list of recommended non-monorepo package groupings
• Fix some problems with very old Maven commons versions
• Ignore spring cloud 1.x releases
• Ignore http4s digest-based 1.x milestones
• Use node versioning for @types/node
• Limit concurrent requests to reduce load on Repology servers until we can fix this properly, see issue 10133

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.

What to Expect

With your current configuration, Renovate will create 5 Pull Requests:

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam the project. See docs for prhourlylimit for details.

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.

This PR has been generated by WhiteSource Renovate. View repository job log here.

Hi. Currently, I'm using https://github.com/antfu/ni and it supports all 4 package managers: npm, yarn, pnpm and bun. So I wish that dum it can detect bun.lockb file and have bun option when you do dum i :)

Program currently spreading/expanding quoted, multi-word arguments instead of forwarding them to script.

Changes

• AppArgs now stores arguments in a Vec<String> rather than a String
• Introduces new crate, shlex, to correctly parse arguments passed in interactive mode into a Vec<String>
• Changes run_command function to correctly forward the arguments
• If user passes invalid arguments in interactive mode ( such as leaving an open quote ) the user is warned and prompted again until the user passes valid arguments or exits

Behavior before changes

dum run foo "first arg" "second"
$ foo
$ node stuff/example-script first arg second
from example [ 'first', 'arg', 'second' ] # ❌ 3 arguments

Behavior after changes (desired behavior)

dum run foo "first arg" "second"
$ foo
$ node stuff/example-script "first arg" second
from example [ 'first arg', 'second' ] # ✅ 2 arguments

Fixes

fixes #59

Description

Program currently spreading/expanding quoted, multi-word arguments instead of forwarding them to script.

How to reproduce bug

Run the following command after cloning the repository:

dum run foo 'first arg' 'second'

Expected behavior

from example [ 'first arg', 'second' ]

Actual behavior

from example [ 'first', 'arg', 'second' ]

This would let me put it in front of yarn very easily:

function yarn() {
  dum --fail-on-missing-command "$@" || $YARN_BIN "$@" 
}