Repository navigation
bug: envvars.update() throws "ReferenceError: name is not defined" outside a task context #4264
Description
Activity
- changed the title
[-]envvars.update() throws "ReferenceError: name is not defined" outside a task context[/-][+]bug: envvars.update() throws "ReferenceError: name is not defined" outside a task context[/+]on Jul 15, 2026 Confirming on the latest as asked — still broken on
@trigger.dev/sdk@4.5.13:ERROR: ReferenceError: name is not definedcreate()from the same script reaches the network layer (AuthenticationError: Invalid API keywith a dummy token), so the failure is specific toupdate()and happens before any request is made.The line is in the non-task branch of
update()in the publisheddist/commonjs/v3/envvars.js:function update(projectRefOrName, slugOrParams, nameOrRequestOptions, params, requestOptions) { ... } else { $projectRef = projectRefOrName; $slug = slugOrParams; $name = name; // <- no `name` parameter exists $params = params; }
The third parameter is
nameOrRequestOptions, sonameresolves to nothing and throws. It should be:$name = nameOrRequestOptions;
typeof nameOrRequestOptions === "string"is probably worth asserting there too, since that branch has already established the 4-arg form.Why only this path: the other methods never reference a bare
name, and inside a task run thetaskContext.ctxbranch is taken instead, which assigns$namefrom real parameters. So it only surfaces outside a task, which matches the report exactly. (In a browser this would silently pick upwindow.namerather than throwing — Node has no such global, which is why it's a hard error here.)One other thing worth a look while that function is open — the first task-context branch assigns both from the same argument:
$projectRef = slugOrParams; $slug = slugOrParams ?? taskContext.ctx.environment.slug;
$projectReftakingslugOrParamslooks unintended given the parameter names, though I haven't exercised that path so I can't say what the intended behaviour is.
Env Info
Description
Calling
envvars.update(projectRef, slug, name, params)from outside a task run (a plain Node script / CI deploy step) always throwsReferenceError: name is not defined.envvars.create,del,retrieve, andlistall work fine from the same context.SDK version
@trigger.dev/sdk4.5.0. The code path looks unchanged in the publisheddist, so 4.5.x is likely affected too — please confirm on the latest.Reproduction
Root cause
update(projectRefOrName, slugOrParams, nameOrRequestOptions, params, requestOptions)— the non-task-context branch resolves the name as:Unlike
del/retrieve(whose third positional parameter is literally namedname),update's third parameter isnameOrRequestOptions, sonameis not in scope and the call throws. The in-task-context branch is correct.For reference, the compiled
dist/commonjs/v3/envvars.jsupdate()non-task branch:Suggested fix
(matching how
$projectRef/$slug/$paramsare resolved from the positional args in the same branch).Impact / workaround
envvars.update()is unusable from the management-API path (e.g. updating an env var from a deploy script). Workaround:envvars.del()followed byenvvars.create().create,del,retrieve, andlistare unaffected.