fix: bash completion script

[Foo-x]

What does this PR do?

#6037

Fixed the bash completion script to complete scripts in package.json.

• local scripts="${matched%%\}*}"; didn't work if scripts contained } characters.
• Since re_comp_word_script was not defined, the condition ( "${COMPREPLY[*]}" =~ ${re_comp_word_script} ) was always true and completions for scripts were removed.

---

• Documentation or TypeScript types (it's okay to leave the rest blank in this case)
• Code changes

How did you verify your code works?

package.json

before	after

[RiskyMH]

This appears to work. But the whole bash completions feel buggy. I don't think it was this pr, but folders aren't autocompleting for me in bun run (it only accepts files or the scripts).

Also bun build and some other commands now have the package.json scripts which is odd.

[RiskyMH]

Also just found out that there are other bun cli commands you can use instead of reading yourself.

For example bun getcompletes s seems to be package.json scripts:

bun/completions/bun.zsh

Lines 674 to 677 in c2edbe8

	local -a scripts_list
	IFS=$'\n' scripts_list=($(SHELL=zsh bun getcompletes i))
	scripts="scripts:scripts:((${scripts_list//:/\\\\:}))"
	IFS=$'\n' files_list=($(SHELL=zsh bun getcompletes j))

bun/completions/bun.zsh

Lines 873 to 874 in c2edbe8

	IFS=$'\n' scripts_list=($(SHELL=zsh bun getcompletes s))
	IFS=$'\n' bins=($(SHELL=zsh bun getcompletes b))

bun/completions/bun.zsh

Line 920 in c2edbe8

IFS=$'\n' packages=($(SHELL=zsh bun getcompletes a $words[$CURRENT]))

bun/completions/bun.fish

Line 16 in c2edbe8

string trim (string split '\n' (string split '\t' (bun getcompletes z)))

bun/completions/spec.yaml

Line 24 in c2edbe8

SHELL=zsh bun getcompletes r

---

bun/src/cli.zig

Lines 1946 to 1962 in c2edbe8

	if (filter.len == 0) {
	completions = try RunCommand.completions(ctx, &default_completions_list, &reject_list, .all);
	} else if (strings.eqlComptime(filter[0], "s")) {
	completions = try RunCommand.completions(ctx, null, &reject_list, .script);
	} else if (strings.eqlComptime(filter[0], "i")) {
	completions = try RunCommand.completions(ctx, &default_completions_list, &reject_list, .script_exclude);
	} else if (strings.eqlComptime(filter[0], "b")) {
	completions = try RunCommand.completions(ctx, null, &reject_list, .bin);
	} else if (strings.eqlComptime(filter[0], "r")) {
	completions = try RunCommand.completions(ctx, null, &reject_list, .all);
	} else if (strings.eqlComptime(filter[0], "g")) {
	completions = try RunCommand.completions(ctx, null, &reject_list, .all_plus_bun_js);
	} else if (strings.eqlComptime(filter[0], "j")) {
	completions = try RunCommand.completions(ctx, null, &reject_list, .bun_js);
	} else if (strings.eqlComptime(filter[0], "z")) {
	completions = try RunCommand.completions(ctx, null, &reject_list, .script_and_descriptions);
	} else if (strings.eqlComptime(filter[0], "a")) {

[Foo-x]

Updated to use bun getcompletes s.

But the whole bash completions feel buggy.

Yeah, currently there are a lot of bugs, e.g. it can't complete a script which has : like test:coverage.
If the whole file need to be rewritten, I will close this pull request. Is that better?

[RiskyMH]

i think its still a good improvement, only thing that i dont think is wise is bun build showing pkg scripts, but otherwise nice :)

full fix could be later

[Foo-x]

OK, I have fixed to read package.json scripts only on bun run!