office-addin-debugging
Advanced tools
This package provides the orchestration of components related to debugging Office Add-ins. When debugging is started, it will ensure that the dev-server is running, that dev settings are configured for debugging, and will register and sideload the Office Add-in. When debugging is stopped, it will unregister and shutdown components.
Starts debugging.
Syntax:
office-addin-debugging start <manifest> [platform] [options]
manifest: path to manifest file.
platform: which type of application:
desktop: Office app for Windows or Macweb: Office app in the web browserNotes:
The dev server is needed to download the add-in from the source location specified in the manifest.
--packager is needed unless --debug-method is direct and --no-live-reload is specified.
Options:
--app <app>
Specifies which Office app to use:
excelonenoteoutlookprojectpowerpointwordIf this is not specified, the behavior depends on the <Hosts> specified in the manifest.
For a single host, it will automatically start that Office app.
For multiple hosts, it will prompt to choose the desired host.
--debug-method <method>
Specifies which debug method to use:
direct: debug directly using the JavaScript engine.web: debug using the JavaScript engine in a web browser or Node.--dev-server <command>
Specifies to run the dev server using the specified command.
--dev-server-port <port>
Specifies the port for the dev server. If provided, the dev server is only started if not already running.
--document
Specifies the document to sideload. The document option can either be the local path to a document or a url.
--no-debug
Start without debugging.
--no-live-reload
Do not enable live-reload.
--no-sideload
Do not start the Office app and load the Office add-in.
--packager <command>
If this option is provided, the packager is started with the specified command.
--packager-host <host>
Host name of the packager. Default: localhost.
--packager-port <port>
Port number of the packager. Default: 8081.
--prod
Specifies that debugging session is for production mode. Default is development mode.
--source-bundle-url-host <host>
Host name to obtain the source bundle. Default: localhost.
--source-bundle-url-port <port>
Port number to obtain the source bundle. Default: 8081.
--source-bundle-url-path <path>
Path used to obtain the source bundle.
--source-bundle-url-extension <extension>
Extension used to obtain the source bundle. Default: .bundle.
-h, --help
Output usage information.
Stops debugging.
Syntax:
office-addin-debugging stop <manifest> [options]
manifest: path to manifest file.
Options:
--prod
Specifies that debugging session is for production mode. Default is development mode.
FAQs
For debugging Office Add-ins.
The npm package office-addin-debugging receives a total of 27,585 weekly downloads. As such, office-addin-debugging popularity was classified as popular.
We found that office-addin-debugging demonstrated a healthy version release cadence and project activity because the last version was released less than 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
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.