fix(js-sdk): parse Dockerfile ENV/ARG values with spaces

[eeshsaxena]

Problem

The JS SDK's Dockerfile parser (Template.fromDockerfile) parsed each ENV/ARG argument token in isolation. dockerfile-ast splits arguments on whitespace — including inside quotes — so a value with a space landed in the "traditional key value" branch and produced a malformed key.

// Dockerfile:  ENV NAME="John Doe"
// dockerfile-ast tokens: ["NAME=\"John", "Doe\""]
//
// before: env var  {'NAME="John': 'Doe"'}   ❌
// after:  env var  { NAME: 'John Doe' }      ✔

This breaks the standard, documented way to put a space in an env value. ENV KEY=hello world was affected too. The Python SDK already parses these correctly (regex on the raw string + quote strip), so the same Dockerfile produced different env vars depending on which SDK you used.

Fix

Rejoin the tokens and parse the raw value the same way as the Python SDK:

• key=value form: a value runs across whitespace until the next key= token; surrounding quotes are stripped.
• key value form unchanged; multiple key=value pairs on one line stay separated.

const template = Template().fromDockerfile(`FROM node:24
ENV NAME="John Doe"
ENV GREETING=hello world
ENV A=1 B=2`)
// NAME     -> "John Doe"
// GREETING -> "hello world"
// A -> "1", B -> "2"

Notes

• Only the JS SDK is changed; this brings it in line with the already-correct Python implementation, so no Python change is needed.
• Added a fromDockerfile test asserting the quoted, spaced, and multi-pair cases, plus a changeset. I verified the new parser against dockerfile-ast's real tokenization for all the cases above; the monorepo install was too slow to run the full pnpm test locally, so CI runs the suite.

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have @eeshsaxena on file. You can sign our CLA at https://e2b.dev/docs/cla . Once you've signed, post a comment here that says '@cla-bot check'

[changeset-bot]

🦋 Changeset detected

Latest commit: c17ca80

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
e2b	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[devin-ai-integration]

Checked cross-language parity (T-1/T-2), enum dispatch (T-15/T-41), template-builder conventions (T-37–T-43), and public API/documentation rules; 0 violations found in the changed code.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c17ca80d87

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Preserve legacy ENV values containing equals signs

Docker's legacy ENV <key> <value> form permits = inside the value, but selecting the assignment form whenever the whole line contains = misparses ENV KEY value=foo as { value: "foo" } and drops KEY; the parent implementation's two-token branch correctly produced KEY=value=foo. Determine the syntax from the leading token rather than from any equals sign in the joined value, and make the equivalent correction in the shared Python parser, which currently uses the same faulty test.

AGENTS.md reference: AGENTS.md:L3-L3

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Preserve punctuation in ENV variable names

Docker ENV keys are not restricted to JavaScript's ASCII \w class, so a valid instruction such as ENV com.example.setting=on is now parsed as { setting: "on" }; similarly, ENV MY-VAR=value becomes VAR=value. The previous substring(0, equalIndex) logic preserved these names, so the matcher should capture the complete non-whitespace key before = and the equivalent Python regex should be corrected as well.

AGENTS.md reference: AGENTS.md:L3-L3

Useful? React with 👍 / 👎.