Registry / devops / nexe-webpack-plugin

nexe-webpack-plugin

library0.1.1jsnpmunverified

Webpack plugin that emits a binary package compiled by nexe, integrating the Nexe JavaScript-to-binary compiler into webpack builds. Current stable version is 0.1.1 with limited release cadence. Key differentiator: allows creating standalone executables from webpack bundles. Requires webpack ^4.0.0 as a peer dependency. Ships TypeScript types. Suitable for developers who need to distribute Node.js applications as single binaries.

devops

npm install nexe-webpack-plugin

github ↗package ↗

INSTALL

IMPORT

SIG · NEXE-WEBPACK-PLUGI

nexe-webpack-plugin

devopsjavascriptv0.1.1

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

NexePlugin

✓ import { NexePlugin } from 'nexe-webpack-plugin'

✗ const NexePlugin = require('nexe-webpack-plugin')

Package ships TypeScript types; named export is the correct import. In CommonJS, use destructuring require.

default import

✓ import { NexePlugin } from 'nexe-webpack-plugin'

✗ import NexePlugin from 'nexe-webpack-plugin'

No default export; only named export NexePlugin.

type import

✓ import type { NexePlugin } from 'nexe-webpack-plugin'

✗ import { NexePlugin } from 'nexe-webpack-plugin' (for type-only usage)

If only using type information in TypeScript, prefer type-only import to avoid bundling code.

Configures webpack to use NexePlugin to compile entry.js into a standalone binary sample-bin.

// webpack.config.js const { NexePlugin } = require('nexe-webpack-plugin'); const { resolve } = require('path'); module.exports = { mode: 'development', entry: './entry.js', output: { path: resolve(__dirname, 'build'), }, plugins: [ new NexePlugin({ output: 'sample-bin', }), ], };

Debug

Known issues

gotchaNexePlugin requires webpack ^4.0.0 as peer dependency — incompatible with webpack 5.

fix

Use webpack 4.x or check for updates that support webpack 5.

affects: >=0.1.0

breakingNo default export — attempting import NexePlugin from 'nexe-webpack-plugin' yields undefined.

fix

Use named import: import { NexePlugin } from 'nexe-webpack-plugin'.

affects: >=0.1.0

gotchaNexe itself may require additional system dependencies (e.g., build tools) that are not documented in this plugin.

fix

Consult nexe documentation for prerequisites.

affects: >=0.1.0

Errors

Common errors & fixes

Error: Cannot find module 'nexe-webpack-plugin'

Package not installed or missing from node_modules.

fix

Run npm install -D nexe-webpack-plugin

TypeError: NexePlugin is not a constructor

Using default import instead of named import.

fix

Change to const { NexePlugin } = require('nexe-webpack-plugin');

Error: Cannot find module 'webpack'

Missing peer dependency webpack.

fix

Run npm install -D webpack@^4.0.0

Upgrade

Version history

0.1.1latest on npm

Audit

Dependencies

webpackrequiredpeer dependency required for plugin functionality

Agent activity

2 hits · last 30 days

node

Resources

githubhttps://github.com/fmatzy/nexe-webpack-plugin ↗

packagehttps://www.npmjs.com/package/nexe-webpack-plugin ↗