npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@smaddock/electron-native-utils

v1.0.0

Published

Additional native utilities for Electron.

Downloads

94

Readme

electron-native-utils

Additional native utilities for Electron.

Building

Requirements

  • Windows: Visual Studio 2022

Commands

  • yarn build - Incremental builds.
  • yarn build:ci - Clean and fully rebuild.
  • yarn build:debug - Debug builds for easier debugging.

Architecture

electron-native-utils uses node-gyp to configure and build .node binaries.

It uses Node-API to provide JavaScript bindings to native code.

Files

  • src/ - contains C++ source and header files
  • lib/index.js - main entry point of the node module
  • lib/index.d.ts - TypeScript type definitions
  • binding.gyp - build config for node-gyp
  • test.js - simple test script to require and invoke the module's API to ensure no crashes occur

API Design

  • Group functionality by namespaces
  • Prefer promises over callbacks for async
  • Reject promises with an Error instead of a string
  • Exported bindings should be available on each platform (Windows, Mac, Linux)
    • When a function returns a promise, it should reject on unsupported platforms.
      Otherwise, it should throw an exception.

Writing cross-platform code

  • Source files can be compiled for specific patterns using a filename postfix.
    • _win - Windows
    • _mac - macOS
    • _linux - Linux
  • Platform-specific macros can be used to export methods which throw on unsupported platforms.
    Napi::Object InitApi(Napi::Env env) {
      Napi::Object exports = Napi::Object::New(env);
      // Method throws on non-Windows platforms.
      METHOD_WIN(winMethodName, WinMethod);
    
      // Method throws on non-MacOS platforms.
      METHOD_MAC(macMethodName, MacMethod);
    
      // Async variants which reject returned promise on unsupported platforms.
      METHOD_ASYNC_WIN(asyncMethod, AsyncMethod);
      METHOD_ASYNC_MAC(asyncMethod, AsyncMethod);
      return exports;
    }
  • Platform defines can be used to conditionally include code.
    #ifdef _WIN32
      // Windows code
    #endif // _WIN32
    
    // OR
    
    #if defined(_WIN32)
      // Windows code
    #elif defined(__APPLE__)
      // Mac code
    #elif defined(__linux__)
      // Linux code
    #endif