Package Exports

auto-launch

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (auto-launch) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

node-auto-launch

[![Build Status][travis-image]][travis-url]

Launch node-webkit apps at login (Mac, Windows and Linux)

Installation

npm install auto-launch

General

So far the api consists only enable disable and isEnabled.

Usage

For node-webkit apps you don't have to specify the path. It gets read from process.execPath :)

var AutoLaunch = require('auto-launch');

var nwAppLauncher = new AutoLaunch({
    name: 'My node webkit app yao'
});

nwAppLauncher.isEnabled(function(enabled){
    if(enabled) return;

    nwAppLauncher.enable(function(err){

    });

});

I added a method (removeNwjsLoginItem) to remove 'nwjs helper' app login item that might have been added to peoples accounts since the name change from node-webkit.

For general apps

var AutoLaunch = require('auto-launch');

var minecraftAutoLauncher = new AutoLaunch({
    name: 'Minecraft',
    path: '/Applications/Minecraft.app',
    isHidden: true // hidden on launch - only works on a mac atm.
});

minecraftAutoLauncher.enable();
//minecraftAutoLauncher.disable();

TODO:

Figure out what's wrong with the damn tests.
Add getCurrentPath - So you can check if the app has moved a roundabout.