debug-adapter-for-office-addins
Advanced tools
Currently building the native code binaries is not part of the process as the tools necessary to to so (windows-build-tools, gulp, prebuild) have some problems (deprication and vulnerabilities). The native code is still here and building could be achievable if these tools were added locally and the build process fixed (updateding the native tooling references probably needed). Update the build script in package.json to be the following:
"build": "npm run build:script && prebuild.cmd && npm run build:native && npm run build:nativeaddon",
"build:script": "npm run clean && npm run lint && npm run build:ts && npm run copy:static",
"build:native": "npm config set msvs_version 2015 && gulp buildnative",
"build:nativeaddon": "npm config set msvs_version 2015 && gulp buildnativeaddon",
"build:ts": "tsc",
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
FAQs
Debug Adapter for Office Add-ins
We found that debug-adapter-for-office-addins 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.
Research
Socket Threat Research maps a rare inside look at OtterCookie’s npm-Vercel-GitHub chain, adding 197 malicious packages and evidence of North Korean operators.
Research
Socket researchers identified a malicious Chrome extension that manipulates Raydium swaps to inject an undisclosed SOL transfer, quietly routing fees to an attacker wallet.
Research
/Security News
Another wave of Shai-Hulud campaign has hit npm with more than 500 packages and 700+ versions affected.