From e75e74815b4625f6b8052a9ea6408a501bc125bb Mon Sep 17 00:00:00 2001 From: Niklas Wenzel Date: Sat, 30 Nov 2024 00:18:18 +0100 Subject: [PATCH] chore: make linter happy I would have preferred to have the space there, but it's fine without, too. --- guides/code-signing/code-signing-windows.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/code-signing/code-signing-windows.md b/guides/code-signing/code-signing-windows.md index 7b8c0f5..4544dda 100644 --- a/guides/code-signing/code-signing-windows.md +++ b/guides/code-signing/code-signing-windows.md @@ -173,7 +173,7 @@ const config: ForgeConfig = { #### Updating your npm scripts -When you call scripts such as `electron-forge make` or `electron-forge publish`, you will now have to prefix them with `dotenv -e .env.trustedsigning -- `. This loads the environment variables from the `.env.trustedsigning` file. +When you call scripts such as `electron-forge make` or `electron-forge publish`, you will now have to prefix them with `dotenv -e .env.trustedsigning --`. This loads the environment variables from the `.env.trustedsigning` file. For example, your npm scripts in your `package.json` might then look like this: