oven-sh/bun

when passing arguments to `bun run` it escapes double quotes

Closed

#7,667 opened on Dec 15, 2023

View on GitHubContributor guide
 (4 comments) (3 reactions) (0 assignees)Rust (4,486 forks)batch import
bugbun installgood first issue

Repository metrics

Stars
 (90,348 stars)
PR merge metrics
 (Avg merge 1d 17h) (357 merged PRs in 30d)

Description

What version of Bun is running?

1.0.18+36c316a24

What platform is your computer?

Linux 5.15.0-58-generic x86_64 x86_64

What steps can reproduce the bug?

  1. add a command containing double quotes to package.json scripts
{
  "scripts": {
    "foo": "echo \"ONE\" TWO",
  }
}
  1. call bun run foo
  2. call bun run foo THREE

What is the expected behavior?

> bun run foo 
$ echo "ONE" TWO
ONE TWO
> bun run foo THREE
$ echo "ONE" TWO THREE
ONE TWO THREE
>

What do you see instead?

> bun run foo 
$ echo "ONE" TWO
ONE TWO
> bun run foo THREE
$ echo \"ONE\" TWO THREE
"ONE" TWO THREE
>

Contributor guide

Research direction
The bug occurs when additional arguments are passed to `bun run`. The discrepancy shows that double quotes are escaped incorrectly when extra args are provided. Investigate the source code responsible for parsing the command from package.json and appending arguments. Look for files related to script execution, e.g., in `packages/bun/` or `cli/`. Check if there's a linked PR or comment addressing this. Consider the shell escaping logic used.
Tech stack
rust
Domain
cli
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScript basicsBun runtime basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50