"office-addin-debugging" is not recognized as an internal or external command.
See original GitHub issueHi, I’m following https://docs.microsoft.com/en-us/office/dev/add-ins/quickstarts/excel-quickstart-jquery?tabs=yeomangenerator. I installed git, nodejs and npm and created the example with yo office
. I’m having the following error:
PS C:\redacted\gits\test\test-1> npm start
> office-addin-taskpane-js@0.0.1 start C:\redacted\gits\test\test-1
> office-addin-debugging start manifest.xml
"office-addin-debugging" non è riconosciuto come comando interno o esterno,
un programma eseguibile o un file batch.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! office-addin-taskpane-js@0.0.1 start: `office-addin-debugging start manifest.xml`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the office-addin-taskpane-js@0.0.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\redacted\AppData\Roaming\npm-cache\_logs\2020-03-15T15_08_25_119Z-debug.log
PS C:\redacted\gits\test\test-1> ls
Content of
C:\Users\redacted\AppData\Roaming\npm-cache\_logs\2020-03-15T15_08_25_119Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'start'
1 verbose cli ]
2 info using npm@6.13.4
3 info using node@v12.16.1
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle office-addin-taskpane-js@0.0.1~prestart: office-addin-taskpane-js@0.0.1
6 info lifecycle office-addin-taskpane-js@0.0.1~start: office-addin-taskpane-js@0.0.1
7 verbose lifecycle office-addin-taskpane-js@0.0.1~start: unsafe-perm in lifecycle true
8 verbose lifecycle office-addin-taskpane-js@0.0.1~start: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\redacted\gits\test\test-1\node_modules\.bin;C:\Python27\;C:\Python27\Scripts;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\ProgramData\Oracle\Java\javapath;C:\Program Files\Intel\iCLS Client\;C:\Windows\System32;C:\Windows;C:\Windows\System32\wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\GnuPG\bin;C:\Program Files\PuTTY\;C:\Program Files (x86)\Infocert\DiKe 6\RAO;C:\Windows\System32\OpenSSH\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Microsoft VS Code\bin;C:\Program Files\dotnet\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Android;C:\Program Files\Git\cmd;C:\Program Files\nodejs\;C:\ProgramData\chocolatey\bin;C:\Users\redacted\AppData\Local\Programs\Python\Python36-32\Scripts\;C:\Users\redacted\AppData\Local\Programs\Python\Python36-32\;C:\Users\redacted\AppData\Local\Programs\Python\Launcher\;C:\Users\redacted\AppData\Local\Microsoft\WindowsApps;C:\Program Files (x86)\Sophos\Sophos SSL VPN Client\bin;C:\Users\redacted\.dotnet\tools;C:\Users\redactedv\AppData\Roaming\npm
9 verbose lifecycle office-addin-taskpane-js@0.0.1~start: CWD: C:\redacted\gits\test\test-1
10 silly lifecycle office-addin-taskpane-js@0.0.1~start: Args: [ '/d /s /c', 'office-addin-debugging start manifest.xml' ]
11 silly lifecycle office-addin-taskpane-js@0.0.1~start: Returned: code: 1 signal: null
12 info lifecycle office-addin-taskpane-js@0.0.1~start: Failed to exec start script
13 verbose stack Error: office-addin-taskpane-js@0.0.1 start: `office-addin-debugging start manifest.xml`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:311:20)
13 verbose stack at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:311:20)
13 verbose stack at maybeClose (internal/child_process.js:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid office-addin-taskpane-js@0.0.1
15 verbose cwd C:\redacted\gits\test\test-1
16 verbose Windows_NT 10.0.18362
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v12.16.1
19 verbose npm v6.13.4
20 error code ELIFECYCLE
21 error errno 1
22 error office-addin-taskpane-js@0.0.1 start: `office-addin-debugging start manifest.xml`
22 error Exit status 1
23 error Failed at the office-addin-taskpane-js@0.0.1 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Do I miss something? maybe in the installation procedure?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:21 (1 by maintainers)
Top Results From Across the Web
Getting "office-addin-debugging is not recognized as an ...
Getting "office-addin-debugging is not recognized as an internal or external command" after running an Excel task pane project with yo office.
Read more >office-addin-debugging - npm
This package provides the orchestration of components related to debugging Office Add-ins. When debugging is started, it will ensure that the ...
Read more >Validate an Office Add-in's manifest - Microsoft Learn
Open a command prompt and install the validator with the following command. command line. Copy. npm install -g office-addin ...
Read more >Office Add-ins with Visual Studio Code
To open your add-in project in VS Code, navigate to the root directory of your add-in project and enter the following on the...
Read more >Troubleshooting — xlwings dev documentation
If you get the error 'python' is not recognized as an internal or external command, operable program or batch file. , then you...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Somehow this fixed it for me: Delete node_module and package-lock.json Add “office-addin-debugging”: “^3.0.34” (or “^4.3.14”) to devDependencies in package.json npm install npm start (as admin if needed)
Had the same issue, but resolved it using