feat: add hidden browser window for execution [INS-3378]

[ihexxa]

Changes:

• add a hidden browser window for running scripts
• enable basic inso fields:
  • variables
  • collectionVariables
  • environment
  • iterationData
  • info
• Add tests or checking APIs of above objects.

How to play with it:

• In the main renderer dev tool console, start the hidden window: await window.hiddenBrowserWindow.start();
• run some scripts

window.postMessage(
    {
      action: 'message-event://hidden.browser-window/debug',
      id: 'simply updating enviroment',
      code: `
        insomnia.environment.set('hello', 'insomnia');
        // or other code
      `,
      context: {
        insomnia: {
          environment: {
            hello: 'world',
          },            
        },
      },
    },
    '*',
    [],
); 

TODO:

• improve the visibility of hidden browser window procedure
• improve the page waiting logic in test.ts
• expose insomnia object for testing if possible

[marckong]

FYI - Electron supports utility process out of the box now - https://www.electronjs.org/docs/latest/api/utility-process

We can take a look at Bloom's implementation. Theirs is pretty straightforward and clean - https://github.com/bloomwalletio/bloom/blob/f69868fc7003248fadb583d3a03a162d5f6d289b/packages/desktop/lib/electron/processes/main.process.ts#L287

[ihexxa]

@marckong Cool, how does it handle Node APIs? Let's have a discussion.

[ihexxa]

message names are basically named in this way protocol://target/action and it might help to understand the workflow.

[jackkav]

can you provide reference documentation for the utility process implementation?
The why of the PR is not particularly clear in the description, so it would be helpful for the future maintainers to list a few thoughts about why you chose this approach and what else you considered.

[ihexxa]

@jackkav It makes sense, I have one and let me update it.

[jackkav]

TODO: (perhaps out of scope) what happens when the hidden window is closed unexpectedly

[jackkav]

an idea for exposing the issues with hidden browser window, would be to allow the insomnia object to be useable inside an insomnia test. That was we can send some simple calculation over the message port in this scope and playwright test it.

[ihexxa]

@jackkav Hidden window health checking is a good point. Current implementation mainly takes care it by following parts:

• when the hidden browser window is closed, it will send out a message-channel://consumers/close message here: https://github.com/Kong/insomnia/pull/6897/files#diff-cf4ec28f994de79ba2cb3c9d96b57c198e7e3ab48e2b1067c5d267fba521f884R74
• the WindowMessageHandler (of the main renderer) will receive this message, and clean and close the channel
• And in this place, before running the pre-request script, it checks if port is invalid, if so, it tries to restart the hidden window immediately

It is an interesting topic let me know if you have thoughts on it and we can have a discussion.

[jackkav]

This PR was broken down into separate PRs #7063 #7070 #7065 Thanks @ihexxa really cool work!