
Security News
Another Round of TEA Protocol Spam Floods npm, But It’s Not a Worm
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.
iojs-bundler
Advanced tools
Bundle io.js in native applications
This module helps you automate including io.js in binary distributions of your software. It handles the downloading of the io.js version you specify, and lets you run npm from within the bundled io.js environment — which is especially important for modules with native add-ons. It's actually kinda tricky to get this working right, so this module exists to make it so you don't have to worry about those details.
While io.js was great, now that io.js and Node.js have merged you may be more interested in node-bundler.
An example, using Gulp, minus proper error handling:
var iojsBundler = require("iojs-bundler")
gulp.task("iojs", function (done) {
var installer = iojsBundler("dist/my.app", "^1.6.4")
installer.install("Resources/ThirdParty/", function (err, installation) {
installation.npm("Resources/my-iojs-app", ["install"], function (err) {
return done()
})
})
})
var iojsBundler = require("iojs-bundler")
Returns a new Installer instance. The targetPath you specify should be the full path to your target application bundle, plugin bundle, etc.
The versionRange is a semver range used to specify the highest allowed version of io.js to install. It probably makes sense to specify a specific version, considering that if a new release of io.js comes out in between runs, you may wind up with two versions installed in your application bundle, consuming unnecessary space.
Downloads and installs the io.js binary distribution in a new directory, named something like iojs-v1.6.4-linux-x64, inside the directory specified by relativeInstallPath. Note that relativeInstallPath is relative to the targetPath parameter given to the iojsBundler() function.
The callback is a function which will be called with an error as its first argument if there was an error during the install process. If there was no error, the second argument will be an Installation instance.
Returns the io.js version number of the installation.
Returns the path of the iojs binary, relative to your application bundle target. You'll probably want to store this string somewhere inside your application bundle, so that your shipped application code can figure where to find the bundled iojs binary.
Runs the bundled npm binary in the context of the io.js installation. You specify npm's current working directory relative to your application bundle target with the cwd parameter. The arguments and options parameters are passed along to the child_process.spawn function that runs npm.
When complete, the callback is called. If npm exits with an error code or signal, the first argument will contain an Error object.
FAQs
Bundle io.js in native applications
The npm package iojs-bundler receives a total of 3 weekly downloads. As such, iojs-bundler popularity was classified as not popular.
We found that iojs-bundler demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.

Security News
PyPI adds Trusted Publishing support for GitLab Self-Managed as adoption reaches 25% of uploads

Research
/Security News
A malicious Chrome extension posing as an Ethereum wallet steals seed phrases by encoding them into Sui transactions, enabling full wallet takeover.