From 84f0ae01440dc09bcfdf7e14c02ca4eaa1dea25e Mon Sep 17 00:00:00 2001 From: Niklas Wenzel Date: Sat, 30 Nov 2024 00:18:18 +0100 Subject: [PATCH] chore: add linter exception --- guides/code-signing/code-signing-windows.md | 1 + 1 file changed, 1 insertion(+) diff --git a/guides/code-signing/code-signing-windows.md b/guides/code-signing/code-signing-windows.md index 7b8c0f5..dd05117 100644 --- a/guides/code-signing/code-signing-windows.md +++ b/guides/code-signing/code-signing-windows.md @@ -173,6 +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. For example, your npm scripts in your `package.json` might then look like this: