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

nexe-natives

v1.0.2

Published

Support modules with natives within NEXE builds

Downloads

175

Readme

NEXE Natives

NEXE automatically bundles resources that often include node modules with natives (i.e. native.node). However, this will cause problems with the compiled binary due to the way the NEXE Virtual FS works. This is demonstrated when the internal NEXE bundled node module attempts to use require() to import a native.node file. In this case an error will be thrown as it will not be found. This is due to require() not looking within the NEXE Virtual FS to resolve the path.

This library allows native modules in the bundled node application to function as expected.

The way this is accomplished is by moving (at run time) the specific node module outside of any paths referenced as 'resources' in the NEXE build options. When the NEXE binary first executes, it copies the module with natives from within the binary to a path on the local file system that is not part of the NEXE Virtual FS and then "requires" it from the copied location.

This library attempts to accomplish this with minimal impact to the original source code. Once implemented, the node application will continue to work both as a NEXE binary and when natively.

This setup does NOT require parallel code bases or any automation to include or modify source files when building the NEXE binary.

Install

npm install --save nexe-natives

Implementation Example

Original NON working implementation of node-pty:

const pty = require('node-pty');

Modifications to original to allow NEXE binary to use the node-pty library:

const pty = require('nexe-natives')(require.resolve('node-pty'));

Reference

# NexeNatives(modulePath, opts)

  • modulePath: [String] Absolute path to module directory or to a file within module directory
  • opts: [Object]
    • localPath: [String] Directory path to where modules should be stored in local file system (defaults to $HOME/.nexe_natives)
    • removeOnExit: [Boolean] Remove copied module path from local file system when process terminates (defaults to true)

Example 1:

const pty = require('nexe-natives')(require.resolve('node-pty'));

Example 2:

const os = require('os');
const path = require('path');

const pty = require('nexe-natives')(path.join(__dirname, '..', 'node_modules', 'node-pty'), {
  localPath: os.tempdir(),
  removeOnExit: true,
});

License

The MIT License (MIT)

Copyright (c) 2020

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.