This means you possibly can return a Promise if you need to do something asynchronous, e.g. Socket.connect(), and guarantees that you just won’t miss any early calls. The first argument, stage, is a string specifying both early or late, useful for understanding if Gadget was simply loaded, or the script is being reloaded. The second argument, parameters, is the object optionally specified within the configuration file, or an empty object if not. For higher management, such as customized authentication, per-node ACLs, and application-specific protocol messages, you could additionally instantiate the PortalService object as an alternative of running the frida-portal CLI …