[cli-kit] Support parsing multiline environment variables in .env file

[aswamy]

WHY are these changes introduced?

Hydrogen CLI is introducing multiline support in their .env files

• The current library used in cli-kit does not support it
• However, we can't fully remove the old library since it still provides the ability to write to .env files (which the new one does not)

WHAT is this pull request doing?

• Adding dotenv library

How to test your changes?

• Just ensure exists unit tests are run, and the new one passes as well

Post-release steps

Measuring impact

How do we know this change was effective? Please choose one:

• n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
• Existing analytics will cater for this addition
• PR includes analytics changes to measure impact

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes
• I've made sure that any changes to dev or deploy have been reflected in the internal flowchart.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	73.7% (+0.16% 🔼)	6605/8962
🟡	Branches	70.48% (+0.16% 🔼)	3213/4559
🟡	Functions	73.09% (+0.27% 🔼)	1741/2382
🟡	Lines	74.7% (+0.17% 🔼)	6231/8341

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟢	... / context.ts	90% (+0.2% 🔼)	86.84% (-0.49% 🔻)	82.86%	90.56% (+0.21% 🔼)
🔴	... / draftable-extension.ts	31.82% (-5.02% 🔻)	16.67% (-8.33% 🔻)	16.67%	35% (-3.89% 🔻)
🟢	... / setup-dev-processes.ts	94.87% (-0.25% 🔻)	68.18%	90%	94.12% (-0.33% 🔻)
🟢	... / push.ts	92.31% (-0.55% 🔻)	75%	100%	92.31% (-0.55% 🔻)
🟢	... / ConcurrentOutput.tsx	97.62% (-2.38% 🔻)	75% (-8.33% 🔻)	100%	97.44% (-2.56% 🔻)

Test suite run success

1580 tests passing in 737 suites.

Report generated by 🧪jest coverage report action from 3affd6b

[gonzaloriestra]

LGTM, thanks for taking care of it!

Have you tested it on Windows? I'm a bit concerned about the new line logic that works differently there.

[github-actions]

Differences in type declarations

We detected differences in the type declarations generated by Typescript for this branch compared to the baseline ('main' branch). Please, review them to ensure they are backward-compatible. Here are some important things to keep in mind:

• Some seemingly private modules might be re-exported through public modules.
• If the branch is behind main you might see odd diffs, rebase main into this branch.

New type declarations

We found no new type declarations in this PR

Existing type declarations

packages/cli-kit/dist/public/node/dot-env.d.ts

@@ -32,4 +32,5 @@ export declare function writeDotEnv(file: DotEnvFile): Promise<void>;
  */
 export declare function patchEnvFile(envFileContent: string | null, updatedValues: {
     [key: string]: string | undefined;
-}): string;
\ No newline at end of file
+}): string;
+export declare function createDotEnvFileLine(key: string, value?: string, quote?: string): string;
\ No newline at end of file

[aswamy]

Have you tested it on Windows? I'm a bit concerned about the new line logic that works differently there.

@gonzaloriestra

• The dotenv library supports windows new lines so we don't have to worry about the parse method.
• For the writeDotEnv method, i looked at how envfile did their stringify method; they didn't specify OS-level newline characters either, so i think we're fine. See here.
• The patchEnvFile always split the file by \n instead of \r\n so i think we're fine again