Creating a New Electron Browser Module

Welcome to the Electron API guide! If you are unfamiliar with creating a new Electron API module within the browser directory, this guide serves as a checklist for some of the necessary steps that you will need to implement.

This is not a comprehensive end-all guide to creating an Electron Browser API, rather an outline documenting some of the more unintuitive steps.

Add your files to Electron’s project configuration

Electron uses GN as a meta build system to generate files for its compiler, Ninja. This means that in order to tell Electron to compile your code, we have to add your API’s code and header file names into filenames.gni.

You will need to append your API file names alphabetically into the appropriate files like so:

filenames.gni

  1. lib_sources = [
  2.     "path/to/api/api_name.cc",
  3.     "path/to/api/api_name.h",
  4. ]
  6. lib_sources_mac = [
  7.     "path/to/api/api_name_mac.h",
  8.     "path/to/api/api_name_mac.mm",
  9. ]
  11. lib_sources_win = [
  12.     "path/to/api/api_name_win.cc",
  13.     "path/to/api/api_name_win.h",
  14. ]
  16. lib_sources_linux = [
  17.     "path/to/api/api_name_linux.cc",
  18.     "path/to/api/api_name_linux.h",
  19. ]

Note that the Windows, macOS and Linux array additions are optional and should only be added if your API has specific platform implementations.

Create API documentation

Type definitions are generated by Electron using @electron/docs-parser and @electron/typescript-definitions. This step is necessary to ensure consistency across Electron’s API documentation. This means that for your API type definition to appear in the electron.d.ts file, we must create a .md file. Examples can be found in this folder.

Set up ObjectTemplateBuilder and Wrappable

Electron constructs its modules using object_template_builder.

wrappable is a base class for C++ objects that have corresponding v8 wrapper objects.

Here is a basic example of code that you may need to add, in order to incorporate object_template_builder and wrappable into your API. For further reference, you can find more implementations here.

In your api_name.h file:

api_name.h

  2. #ifndef ELECTRON_SHELL_BROWSER_API_ELECTRON_API_{API_NAME}_H_
  3. #define ELECTRON_SHELL_BROWSER_API_ELECTRON_API_{API_NAME}_H_
  5. #include "gin/handle.h"
  6. #include "gin/wrappable.h"
  8. namespace electron {
  10. namespace api {
  12. class ApiName : public gin::Wrappable<ApiName>  {
  13.  public:
  14.   static gin::Handle<ApiName> Create(v8::Isolate* isolate);
  16.   // gin::Wrappable
  17.   static gin::WrapperInfo kWrapperInfo;
  18.   gin::ObjectTemplateBuilder GetObjectTemplateBuilder(
  19.       v8::Isolate* isolate) override;
  20.   const char* GetTypeName() override;
  21. } // namespace api
  22. } // namespace electron

In your api_name.cc file:

api_name.cc

  1. #include "shell/browser/api/electron_api_safe_storage.h"
  3. #include "shell/browser/browser.h"
  4. #include "shell/common/gin_converters/base_converter.h"
  5. #include "shell/common/gin_converters/callback_converter.h"
  6. #include "shell/common/gin_helper/dictionary.h"
  7. #include "shell/common/gin_helper/object_template_builder.h"
  8. #include "shell/common/node_includes.h"
  9. #include "shell/common/platform_util.h"
  11. namespace electron {
  13. namespace api {
  15. gin::WrapperInfo ApiName::kWrapperInfo = {gin::kEmbedderNativeGin};
  17. gin::ObjectTemplateBuilder ApiName::GetObjectTemplateBuilder(
  18.     v8::Isolate* isolate) {
  19.   return gin::ObjectTemplateBuilder(isolate)
  20.       .SetMethod("methodName", &ApiName::methodName);
  21. }
  23. const char* ApiName::GetTypeName() {
  24.   return "ApiName";
  25. }
  27. // static
  28. gin::Handle<ApiName> ApiName::Create(v8::Isolate* isolate) {
  29.   return gin::CreateHandle(isolate, new ApiName());
  30. }
  32. } // namespace api
  34. } // namespace electron
  36. namespace {
  38. void Initialize(v8::Local<v8::Object> exports,
  39.                 v8::Local<v8::Value> unused,
  40.                 v8::Local<v8::Context> context,
  41.                 void* priv) {
  42.   v8::Isolate* isolate = context->GetIsolate();
  43.   gin_helper::Dictionary dict(isolate, exports);
  44.   dict.Set("apiName", electron::api::ApiName::Create(isolate));
  45. }
  47. }  // namespace

In the typings/internal-ambient.d.ts file, we need to append a new property onto the Process interface like so:

typings/internal-ambient.d.ts

  1. interface Process {
  2.     _linkedBinding(name: 'electron_browser_{api_name}', Electron.ApiName);
  3. }

At the very bottom of your api_name.cc file:

api_name.cc

  1. NODE_LINKED_MODULE_CONTEXT_AWARE(electron_browser_{api_name},Initialize)

In your shell/common/node_bindings.cc file, add your node binding name to Electron’s built-in modules.

shell/common/node_bindings.cc

  1. #define ELECTRON_BROWSER_MODULES(V)      \
  2.   V(electron_browser_{api_name})

Note: More technical details on how Node links with Electron can be found on our blog.

Expose your API to TypeScript

Export your API as a module

We will need to create a new TypeScript file in the path that follows:

"lib/browser/api/{electron_browser_{api_name}}.ts"

An example of the contents of this file can be found here.

Expose your module to TypeScript

Add your module to the module list found at "lib/browser/api/module-list.ts" like so:

lib/browser/api/module-list.ts

  1. export const browserModuleList: ElectronInternal.ModuleEntry[] = [
  2.   { name: 'apiName', loader: () => require('./api-name') },
  3. ];