Skip to content

fix: handle potential undefined value for envVars #336

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
roerohan wants to merge 1 commit into from
Closed

fix: handle potential undefined value for envVars #336

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion packages/sandbox/src/sandbox.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -286,7 +286,7 @@ export class Sandbox<Env = unknown> extends Container<Env> implements ISandbox {
if (this.defaultSession) {
// Set environment variables by executing export commands in the existing session
for (const [key, value] of Object.entries(envVars)) {
const escapedValue = value.replace(/'/g, "'\\''");
const escapedValue = value?.replace(/'/g, "'\\''");
const exportCommand = `export ${key}='${escapedValue}'`;

const result = await this.client.commands.execute(
Expand Down
Loading