Meet npm Pro: unlimited public & private packages + package-based permissions.Learn more »


0.0.1 • Public • Published


Development tools for creating Office Add-ins on Windows and Mac. office-addin aims to reduce a few particular pain points related to Office Add-in development:

  1. Setup manifest for sideloading during development
  2. Generating an Add-in manifest
  3. Validating an Add-in manifest
  4. Logging and error handling in Add-ins


Install office-addin as a development dependency for your project.

npm install --save-dev office-addin

The most straight-forward way to call the office-addin command-line tools is from package.json scripts. The following is an example scripts section of a project's package.json.

  "scripts": {
    "setup": "office-addin setup",
    "generate": "office-addin generate",
    "validate": "office-addin validate"


Initial setup for an Office Add-in can be extensive, office-addin setup aims to make it a straightforward, simple process.

# Windows: Run as administrator 
npm run setup
# Mac 
sudo npm run setup

Setup performs the following steps:

  1. (Windows-only) Create .addin-catalog folder in User directory
  2. (Windows-only) Share .addin-catalog for access from Office
  3. Create symlink to Add-in manifest in catalog directory
  4. Generate development https certificates and register as trusted CA
  5. Instructions for loading add-in based on system type

Note: If manifest is generated after setup has been run initially, setup will need to be run again to create symlink of manifest.


office-addin generate is used to get you started with a valid Add-in manifest with required information completed. Additionally, it can be used to create matching manifests that handle differences between development and production.


office-addin validate checks the project's manifest against Microsoft's Add-in schema and verifies that the Add-in can be submitted to the Office Add-in Store.


office-addin can be used to output console.log and errors to the command line. There are two primary components to command line logging: server-side and client-side.

Server-side, attach the logging server to an existing node http server:

const server = ...
const addinServer = require('office-addin/server')();
// Standalone (create server and attach to given port)

Alternative, run a standalone logging server

  "scripts": {
    "start": "office-addin server"

Client-side, include office-addin (preferably before the project's js to catch compilation errors)

import 'office-addin';

For details on usage with Webpack, Gulp, create-react-app, and other environments, see the examples.


npm i office-addin

DownloadsWeekly Downloads






Last publish


  • avatar