Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

CommandLine.template accepts NAME+=value as the program name

Open
#9,862 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
cli

Research direction

Start by reading CommandLine.template and its existing syntax tests, then check how ChildProcess.make uses the parsed template. Add coverage for NAME+=value in the program position and confirm it is rejected as an assignment requiring a shell. The issue author says they already have a fix and plan to open a PR, so check the issue for that work before starting.

Written by the indexing model from the issue text.

Description

CommandLine.template rejects a variable assignment in the program position, but only the NAME=value form. The append form NAME+=value, which bash and zsh (and macOS sh) also read as an assignment, is accepted and becomes the program name:

import { CommandLine } from "effect/process"

CommandLine.template`FOO=bar make`
// Failure: UnsupportedSyntax "A variable assignment needs a shell"

CommandLine.template`FOO+=bar make`
// Success: ["FOO+=bar", "make"]

In bash or zsh, FOO+=bar make runs make with FOO set. ChildProcess.make splits its template with CommandLine.template, so ChildProcess.make`FOO+=bar make` tries to run a program named FOO+=bar instead.

On v4/next-minor (unreleased, added in #9752). I have a small fix with a test and will open a PR.

Dominant language
TypeScript
Stars
16.7k
Forks
808
Avg merge
11h 24m
Merged PRs (30d)
848

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Effect-TS/effect

All issues in Effect-TS/effect

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.