[Bug]: Cannot find native binding when using @tego/botjs in Electron application

[6xiaoxin]

Version

0.2.0

Description of the issue

After installing @tego/botjs in my Electron project, the application fails to load and throws a "Cannot find native binding" error. The error suggests npm's optional dependency bug, but the issue persists even after cleaning dependencies and re-installing. The core problem is that the native module of @tego/botjs is not compatible with Electron's built-in Node.js environment.

@tego/botjs should be loaded normally in the Electron environment, without native binding missing errors.

Steps to reproduce

Steps to reproduce the behavior:

1. Create a new Electron project (my version: 33.4.11)
2. Initialize package.json (Node.js version: 25.1.0)
3. Install @tego/botjs via pnpm add @tego/botjs (or npm install @tego/botjs)
4. Try to start the Electron app (pnpm run dev)
5. The app crashes with the "Cannot find native binding" error

Logs or error messages

App threw an error during load
Error: Cannot find native binding. npm has a bug related to optional dependencies (https://github.com/npm/cli/issues/4828). Please try `npm i` again after removing both package-lock.json and node_modules directory.
    at file:///E:/code/electron/xunfei-dll-no-server/dist-electron/main-DEyYWW85.js:27093:11
    at ModuleJob.run (node:internal/modules/esm/module_job:234:25)
    at async ModuleLoader.import (node:internal/modules/esm/loader:473:24)
    at async loadApplicationPackage (file:///E:/code/electron/xunfei-dll-no-server/node_modules/.pnpm/electron@33.4.11/node_modules/electron/dist/resources/default_app.asar/main.js:129:9)
    at async file:///E:/code/electron/xunfei-dll-no-server/node_modules/.pnpm/electron@33.4.11/node_modules/electron/dist/resources/default_app.asar/main.js:242:9

Environment

• OS: Windows 11
• Node.js Version: v25.1.0
• Electron Version: 33.4.11
• @tego/botjs Version: 0.2.0
• Package Manager: pnpm 10.20.0
• Electron Builder Version : 25.1.8

Checklist

• I have searched existing issues
• I am using the latest version

[sealday]

Apologies, Electron support is currently unavailable. I will investigate this and address it soon.

[sealday]

I've tested this in Electron Fiddle, and it works correctly. Perhaps I need a more detailed process outlined in your instructions.

[sealday]

I tried with Node.js 20.18.3, Chromium 130.0.6723.191, and Electron 33.4.11.

// Modules to control application life and create native browser window
const { app, BrowserWindow } = require('electron');
const fs = require("fs");
const path = require("path");

function createWindow() {
  // Create the browser window.
  const mainWindow = new BrowserWindow({
    width: 800,
    height: 600,
    webPreferences: {
      preload: path.join(__dirname, 'preload.js')
    }
  });

  // and load the index.html of the app.
  mainWindow.loadFile('index.html');

  // Open the DevTools.
  // mainWindow.webContents.openDevTools()
}

// This method will be called when Electron has finished
// initialization and is ready to create browser windows.
// Some APIs can only be used after this event occurs.
app.whenReady().then(async () => {
  // HERE
  const { captureScreen } = await import('@tego/botjs');

  try {
    const screenshot = await captureScreen();
    fs.writeFileSync('screenshot.png', screenshot.image);
    console.log('success');
  } catch (err) {
    console.warn(err);
  }

  createWindow();

  app.on('activate', function () {
    // On macOS it's common to re-create a window in the app when the
    // dock icon is clicked and there are no other windows open.
    if (BrowserWindow.getAllWindows().length === 0) createWindow();
  });
});

// Quit when all windows are closed, except on macOS. There, it's common
// for applications and their menu bar to stay active until the user quits
// explicitly with Cmd + Q.
app.on('window-all-closed', function () {
  if (process.platform !== 'darwin') app.quit();
});

// In this file you can include the rest of your app's specific main process
// code. You can also put them in separate files and require them here.

It does, however, function correctly with a captured screen image. I wonder if this issue is related to pnpm.

[sealday]

Despite using pnpm version 10.18.3 and Electron version 33.4.11, I was still unable to reproduce the error. But recognizing the existing package's substantial size, I initiated a refactoring effort, specifically removing its GUI components, to significantly reduce its overall footprint. You can try 0.2.2.