Closed robcecil closed 2 years ago
D:\Development\local\Commands>npm --verbose run start:web
npm verb cli [
npm verb cli 'C:\\Program Files\\nodejs\\node.exe',
npm verb cli 'C:\\Users\\robc\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
npm verb cli '--verbose',
npm verb cli 'run',
npm verb cli 'start:web'
npm verb cli ]
npm info using npm@7.21.0
npm info using node@v14.17.5
npm timing npm:load:whichnode Completed in 0ms
npm timing config:load:defaults Completed in 1ms
npm timing config:load:file:C:\Users\robc\AppData\Roaming\npm\node_modules\npm\npmrc Completed in 2ms
npm timing config:load:builtin Completed in 2ms
npm timing config:load:cli Completed in 2ms
npm timing config:load:env Completed in 1ms
npm timing config:load:file:D:\Development\local\Commands\.npmrc Completed in 0ms
npm timing config:load:project Completed in 18ms
npm timing config:load:file:C:\Users\robc\.npmrc Completed in 0ms
npm timing config:load:user Completed in 0ms
npm timing config:load:file:C:\Users\robc\AppData\Roaming\npm\etc\npmrc Completed in 1ms
npm timing config:load:global Completed in 1ms
npm timing config:load:validate Completed in 0ms
npm timing config:load:credentials Completed in 2ms
npm timing config:load:setEnvs Completed in 2ms
npm timing config:load Completed in 29ms
npm timing npm:load:configload Completed in 29ms
npm timing npm:load:setTitle Completed in 0ms
npm timing npm:load:setupLog Completed in 1ms
npm timing config:load:flatten Completed in 5ms
npm timing npm:load:cleanupLog Completed in 3ms
npm timing npm:load:configScope Completed in 1ms
npm timing npm:load:projectScope Completed in 27ms
npm timing npm:load Completed in 87ms
[..................] / : timing npm:load Completed in 87ms
> office-addin-taskpane-react@0.0.1 start:web
> office-addin-debugging start manifest.xml web
'office-addin-debugging' is not recognized as an internal or external command,
operable program or batch file.
npm timing command:run-script Completed in 117ms
npm verb exit 1
npm timing npm Completed in 406ms
npm verb code 1
This error suggest that 'npm install' didn't complete as part of the project generation. You should have received and error message to that effect. What was that output of creating the projects using 'yo office'
@millerds :
Looks like it's trying to update the package-lock.json file because you are on npm v7 and it was created with npm v8. This shouldn't be a problem, but there are a ton of warning saying that it can't find the desired version of the necessary packages (not just the ones we publish) even though they are there in npmjs and github websites. I'm not sure what was actually installed as a result.
Can you try running 'npm install' inside the project folder and then the start command? And if that doesn't help can you upgrade to the newest version of node (v16 and npm (v8) and try the process again?
I had already tried the 'npm install' inside the project folder with start command. But I tried again, after removing (using -g) both generator-office and yeoman, and then re-installing, and re-creating a new project as before. Got the same error with 'npm run start:web', even inside the project folder, and after another call to 'install'
added 839 packages, and audited 840 packages in 2m
115 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
----------------------------------------------------------------------------------------------------------
Congratulations! Your add-in has been created! Your next steps:
1. Go the directory where your project was created:
cd D:\Commands
2. Start the local web server and sideload the add-in:
npm start
3. Open the project in VS Code:
code .
For more information, visit http://code.visualstudio.com.
Please visit https://docs.microsoft.com/office/dev/add-ins for more information about Office Add-ins.
----------------------------------------------------------------------------------------------------------
D:\>
D:\>
D:\>cd Commands
D:\Commands>npm run start:web
> office-addin-taskpane-react@0.0.1 start:web
> office-addin-debugging start manifest.xml web
'office-addin-debugging' is not recognized as an internal or external command,
operable program or batch file.
D:\Commands>npm install
up to date, audited 840 packages in 1s
115 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
D:\Commands>npm run start:web
> office-addin-taskpane-react@0.0.1 start:web
> office-addin-debugging start manifest.xml web
'office-addin-debugging' is not recognized as an internal or external command,
operable program or batch file.
OK . . . lets try adding it. Run 'npm install office-addin-debugging --save-dev' in the project folder. Give me the output of that command and the result of running 'npm run start:web' afterward.
D:\Development\local> cd Commands
D:\Development\local\Commands>npm run start:web
> office-addin-taskpane-react@0.0.1 start:web
> office-addin-debugging start manifest.xml web
'office-addin-debugging' is not recognized as an internal or external command,
operable program or batch file.
D:\Development\local\Commands>npm install office-addin-debugging --save-dev
removed 1 package, changed 7 packages, and audited 839 packages in 5s
115 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
D:\Development\local\Commands>npm run start:web
> office-addin-taskpane-react@0.0.1 start:web
> office-addin-debugging start manifest.xml web
Debugging is being started...
App type: web
The dev server is already running on port 3000.
Sideloading the Office Add-in...
Error: Unable to start debugging.
office-addin-debugging: Unable to sideload the Office Add-in.
office-addin-dev-settings: For sideload to web, you need to specify a document url.
Sounds like you are unblocked. We'll have to see if we can figure out why it wasn't getting installed with the other commands.
Expected behavior
Should be able to start a new project via "npm run start:web".
Current behavior
When using the generator to create an Excel Taskpane add-in, including React and Typescript, the resulting project fails to start, but instead logs the error:
Steps to Reproduce
Context
Failure Logs
Please include any relevant log snippets, screenshots or code samples here.