UPDATE 1/9/24: The webpack.config.js change was made in a recent PR. Only the changes to tsconfig.json and package.json still need to be done.

Prerequisites

Please answer the following questions before submitting an issue.
YOU MAY DELETE THE PREREQUISITES SECTION.

• [x ] I am running the latest version of Node and the tools
• [x ] I checked the documentation and found no answer
• [x ] I checked to make sure that this issue has not already been filed

Expected behavior

webpack.config and tsconfig.json does not have unnecessary/confusing settings

Current behavior

The following "rule" is in the webpack.config for this template. This would be relevant for the React version, but not for this version. Having this unneeded loader may confuse devs (like me).

        {
          test: /\.tsx?$/,
          exclude: /node_modules/,
          use: "ts-loader",
        },

The tsconfig.json file has a "jsx" property, with value "react". This "jsx" property should be deleted, because this is not a React project.

Finally, ts-loader should be removed from the package.json. It is not actually doing anything.

I have tested all these changes and the project works fine.

The project needs to be updated to use Webpack v5.

Current behavior

I'm following the Word tutorial HERE and when I run npm start I get the error shown below.

Checking if you have seen this error before and what might be causing it.

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• Operating System: Windows 11
• Node version: v20.11.1

Failure Logs

PS C:\Code\WordAddin> npm start

[email protected] start
office-addin-debugging start manifest.xml

Debugging is being started...
App type: desktop
Enabled debugging for add-in aba61d28-c0a2-4ade-a448-f3673216f4b4.
Starting the dev server... (webpack serve --mode development)
The dev server is running on port 3000. Process id: 14280
Sideloading the Office Add-in...
Error: Unable to start debugging.
Error: Unable to sideload the Office Add-in.
Error: invalid distance too far back

Prerequisites

Please answer the following questions before submitting an issue.
YOU MAY DELETE THE PREREQUISITES SECTION.

• I am running the latest version of Node and the tools
• I checked the documentation and found no answer
• I checked to make sure that this issue has not already been filed

Expected behavior

• <input> should be clickable
• <input> should work

Current behavior

• Even a basic <input> without anything else in the task pane is not clickable / or clickable after multiple tries.
• The autofocus option is not working
• If at some point (with enough tries) you manage to get the focus on an input box then the rest of the session will behave as expected: It's mainly about getting a first "hook" into an "input"

Steps to Reproduce

Please provide detailed steps for reproducing the issue.

1. Open PPT
2. Go to Store Add-ins
3. Search for Gladia
4. Select any "task"
5. Try to click an input

We tried on 10+ machines we were only able to reproduce that on 1 single machine (even after reinstalling PPT from scratch) with the setup described below).

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• Operating System: Apple M1 / macOS Monterey / 16GB
• Node version: v16.16.0
• Office version: Version 16.65 (22091101)
• SSL: On
• Source: Store
• Runtime: Safari WebKit
• Safari: Version 16.0 (17614.1.25.9.10, 17614)
• No Safari extension

Failure Logs

Please include any relevant log snippets, screenshots or code samples here.

=> code

I notice when running yo office that the entire repo gets copied into my new project including the README.md and CONTRIBUTING.md. In the context of a developer creating a new project that does not know there are repos behind the templates, these are awkward when viewing and reading files in the project structure in VS Code.

The readme refers to the repo (but in a new project a developer is likely using their own repo.)
The contributing.md talks about contributing to a sample (but this is a new project, not sample code.)

I recommend moving all the template parts that should get installed into a template folder so you can keep the readme and contributing files separated (or have a different readme that makes sense after you create a new project). Basically the root of the repo would be files specific to this repo and how it operates. Template folder contains the folder/file structure to copy down for new yo office install.

the icon assets/hi-res-icon.png is required by manifest.xml:

<HighResolutionIconUrl DefaultValue="https://localhost:3000/assets/hi-res-icon.png"/>

However, it is not correctly placed while creating the project.

@davidchesnut,

Prerequisites

One Note add-in deployment

Please answer the following questions before submitting an issue.
YOU MAY DELETE THE PREREQUISITES SECTION.

• [X ] I am running the latest version of Node and the tools
• [ X] I checked the documentation and found no answer
• [ X] I checked to make sure that this issue has not already been filed

Expected behavior

Deploy one note add-in in the Organization for specific users or groups

Current behavior

In the Centralized app deployment, I don't see the option to deploy for the One Note add-in, Also, it is integrated with the single sign-on.

Steps to Reproduce

1. Create one note add-in with or single sign-on
2. Deploy add-ins in the organization for specific users or groups

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• Operating System:
• Node version:
• Office version:
• Tool version:

Failure Logs

Please include any relevant log snippets, screenshots or code samples here.

Hi there,

I follow up the Outlook Add-In article [https://learn.microsoft.com/en-us/office/dev/add-ins/quickstarts/outlook-quickstart?tabs=yeomangenerator] to implement my first Outlook Add-In for extracting SharePoint/ Exchange information. My issue plays out on step 1 on [Try it out] section to use the [npm start] command to test the sample. Does anyone have idea on it?

thanks for your effort.

My Environment:

:\Program Files\nodejs
+-- @microsoft/[email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
`-- [email protected]

Please refer to my error message from Visual Studio Code:

npm start

[email protected] start C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane
office-addin-debugging start manifest.xml

internal/modules/cjs/loader.js:905
throw err;
^

Error: Cannot find module 'ajv/dist/core'
Require stack:

C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane\node_modules\ajv-draft-04\dist\index.js
C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane\node_modules\office-addin-manifest\node_modules@microsoft\teams-manifest\build\index.js
C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane\node_modules\office-addin-manifest\lib\export.js
C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane\node_modules\office-addin-manifest\lib\main.js
C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane\node_modules\office-addin-dev-settings\lib\appcontainer.js
C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane\node_modules\office-addin-dev-settings\lib\main.js
C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane\node_modules\office-addin-debugging\lib\commands.js
C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane\node_modules\office-addin-debugging\lib\cli.js
C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane\node_modules\office-addin-debugging\cli.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
at Function.Module._load (internal/modules/cjs/loader.js:746:27)
at Module.require (internal/modules/cjs/loader.js:974:19)
at Module.patchedRequire [as require] (C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane\node_modules\diagnostic-channel\dist\src\patchRequire.js:14:46)
at require (internal/modules/cjs/helpers.js:101:18)
at Object. (C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane\node_modules\ajv-draft-04\dist\index.js:4:16)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:12) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane\node_modules\ajv-draft-04\dist\index.js',
'C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane\node_modules\office-addin-manifest\node_modules\https://github.com/microsoft\teams-manifest\build\index.js',
'C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane\node_modules\office-addin-manifest\lib\export.js',
'C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane\node_modules\office-addin-manifest\lib\main.js',
'C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane\node_modules\office-addin-dev-settings\lib\appcontainer.js',
'C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane\node_modules\office-addin-dev-settings\lib\main.js',
'C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane\node_modules\office-addin-debugging\lib\commands.js',
'C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane\node_modules\office-addin-debugging\lib\cli.js',
'C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane\node_modules\office-addin-debugging\cli.js'
]
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: office-addin-debugging start manifest.xml
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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\Administrator\AppData\Roaming\npm-cache_logs\2023-01-27T14_10_40_745Z-debug.log

The following is my 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 [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]: [email protected]
6 info lifecycle [email protected]: [email protected]
7 verbose lifecycle [email protected]: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]: PATH: C:\Users\Administrator\AppData\Roaming\nvm\v14.19.1\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane\node_modules.bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Windows\System32\OpenSSH;C:\Program Files (x86)\Microsoft SQL Server\150\Tools\Binn;C:\Program Files\Microsoft SQL Server\150\Tools\Binn;C:\Program Files (x86)\Microsoft SQL Server\150\DTS\Binn;C:\Program Files\Microsoft SQL Server\150\DTS\Binn;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn;C:\Program Files\Azure Data Studio\bin;C:\Program Files\dotnet;C:\Program Files\Git\cmd;%NVM_HOME%;%NVM_SYMLINK%;C:\Users\Administrator\AppData\Local\Microsoft\WindowsApps;C:\Users\Administrator.dotnet\tools;C:\Users\Administrator\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\Administrator\AppData\Roaming\nvm;C:\Program Files\nodejs
9 verbose lifecycle [email protected]: CWD: C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane
10 silly lifecycle [email protected]: Args: [ '/d /s /c', 'office-addin-debugging start manifest.xml' ]
11 silly lifecycle [email protected]: Returned: code: 1 signal: null
12 info lifecycle [email protected]: Failed to exec start script
13 verbose stack Error: [email protected] start: office-addin-debugging start manifest.xml
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (C:\Users\Administrator\AppData\Roaming\nvm\v14.19.1\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:400:28)
13 verbose stack at ChildProcess. (C:\Users\Administrator\AppData\Roaming\nvm\v14.19.1\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:400:28)
13 verbose stack at maybeClose (internal/child_process.js:1058:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5)
14 verbose pkgid [email protected]
15 verbose cwd C:\Users\Administrator\source\repos\bitbucket\office\Outlook Add-In\Sample Task-Pane
16 verbose Windows_NT 10.0.17763
17 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start"
18 verbose node v14.19.1
19 verbose npm v6.14.16
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] start: office-addin-debugging start manifest.xml
22 error Exit status 1
23 error Failed at the [email protected] start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Outlook Add-In Error:

This add-in could not be started. Close this dialog to ignore the problem or click "Resatrt" to try again

This localhost page can’t be foundNo webpage was found for the web address: https://localhost:3000/taskpane.html?_host_Info=Outlook$Win32$16.02$en-US$$$$0
HTTP ERROR 404

Prerequisites

Please answer the following questions before submitting an issue.
YOU MAY DELETE THE PREREQUISITES SECTION.

• [x ] I am running the latest version of Node and the tools
• [ x] I checked the documentation and found no answer
• [x ] I checked to make sure that this issue has not already been filed

Expected behavior

When attempting to create an outlook add in with unified manifest for Microsoft 365 it completes

Current behavior

First stage of creating the add in fails at the file it is trying to download does not exist
"Unable to download project zip file for "https://github.com/OfficeDev/Office-Addin-TaskPane/archive/json-preview-yo-office.zip".
AxiosError: Request failed with status code 404"

Steps to Reproduce

Please provide detailed steps for reproducing the issue.

1. yo office
2. Oulook Add-in with unified manifest for Microsoft 365 (preview)
3. Give a name for the add in

Will fail due to the 404 at this stage

Context

Failure Logs

Unable to download project zip file for "https://github.com/OfficeDev/Office-Addin-TaskPane/archive/json-preview-yo-office.zip".
AxiosError: Request failed with status code 404

Hi there!

I've been trying to find a way to make Office-Addin-Taskpane on Desktop (Installed version) and Safari Extension or Chrome Extension to communicate. Would it be possible to do this? I was wondering if you could tell me more about this.

Thank you for your time!

Prerequisites

Please answer the following questions before submitting an issue.
YOU MAY DELETE THE PREREQUISITES SECTION.

• [ x] I am running the latest version of Node and the tools
• [ x] I checked the documentation and found no answer
• [ x] I checked to make sure that this issue has not already been filed

Expected behavior

When a code source file is changed while debugging in VSC, hot reloading should make the change but leave the app in the same place where it was, so the developer doesn't have to go through the all the steps in the UI to get back to where they were.

Current behavior

The change in the source file cause the entire app to reload and returns the app to its default starting state. There is also an error in the VSC debugging console: "Cannot apply update. Need to do a full reload."

Steps to Reproduce

Please provide detailed steps for reproducing the issue.

1. Sideload an add-in in VSC
2. Run the add-in.
3. Make a change in a code source file.

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• Operating System: Windows 10
• Node version: 16.13.2
• Office version: 2302 16127.20000
• Tool version: ?

Failure Logs

Please include any relevant log snippets, screenshots or code samples here.

Since a few days we're observing some odd flexbox behavior with our plugin (e.g. child flexbox divs not properly filling parents anymore). For reproducibility sake I was quickly checking this project out and it definitely doesn't look like it used to.

I reckon the office-ui-fabric-core/11.0.0 was updated underneath, but can't quite make the leap on what happened exactly in the last couple of days.

Current behavior

Just to give you an example from our plugin:

The body stretches the whole panel height, the ms-welcome doesn't want to properly fill the parent anymore:

Steps to Reproduce

Please provide detailed steps for reproducing the issue.

1. checkout this project
2. npm i
3. npm start

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• Operating System: win11
• Node version: 16.15.1 and 18.19.0
• Office version: Office Home/Business 2021, Microsoft® Excel® 2021 MSO (Version 2312 Build 16.0.17126.20132) 64-bit
• Edge Version 120.0.2210.133 (Official build) (64-bit)
• Tool version: cli is at 1.5.7

Failure Logs

nothing, just visuals

Expected behavior

After completing the generation of an add-in prokect, running it was expected to successfully start "webpack dev server".

Current behavior

"Webpack dev server" seems to successfully start in a new window but in the original Terminal window, npm outputs the following errors and exits:

Steps to Reproduce

1. On Windows 10, as per instructions in quickstart installed node LTS (v18.16.0), yo v4.3.1 and latest version of office generator.
2. In an elevated Terminal session, ran yo office and chose Outlook Add-in with unified Microsoft 365 Manifest (preview) as project type.
3. Once generator was done, ran npm start.

Context

• Operating System:
  Windows 10
• Node version:
  LTS (v18.6.0)
• Tool version:
  Yeoman v4.3.1, latest office generator

Failure Logs

Errors appearing in npm output before exit:

running: npx @microsoft/teamsfx-cli m365 sideloading --file-path C:\Users\REDACTED\AppData\Local\Temp\manifest.zip

Using account REDACTED
Uploading package ...
Acquiring package ...
Acquire done. App TitleId: U_e17399ab-af80-a3fc-2780-c43cdf3de208
Checking acquired package ...

--Error sideloading!--
Error: Error: Command failed: npx @microsoft/teamsfx-cli m365 sideloading --file-path C:\Users\REDACTED\AppData\Local\Temp\manifest.zip
This command is in preview.
(×) Sideloading failed.
(×) {"error":{"code":"InternalServerError","message":"There was an error processing the request"}}
(×) [Core.Error]: Request failed with status code 500

STDERR:
This command is in preview.
(×) Sideloading failed.
(×) {"error":{"code":"InternalServerError","message":"There was an error processing the request"}}
(×) [Core.Error]: Request failed with status code 500

Error: Unable to start debugging.
Error: Unable to sideload the Office Add-in.
Error: Command failed: npx @microsoft/teamsfx-cli m365 sideloading --file-path C:\Users\REDACTED\AppData\Local\Temp\manifest.zip
This command is in preview.
(×) Sideloading failed.
(×) {"error":{"code":"InternalServerError","message":"There was an error processing the request"}}
(×) [Core.Error]: Request failed with status code 500

I created an Excel add-in where the user need to log in first to use the add-in functionality.
The login happens in the taskpane.
When the user successfully logged in, I am calling OfficeRuntime.storage.setItems in order to save the user's details (email, token, etc.) in the storage. In Excel web it works properly but in Excel desktop this call fails, and the error returning from the promise is "Unknown: an unknown error has occurred".

The add-in is installed via the store. The Excel version is 2019.
This bug does not happen to all users, only some of them.

• Operating System: Microsoft
• Node version: v10.15.0
• Office version: 2019

This is the function I'm running:

const saveUserInfoInStorage = (token: string) => { return OfficeRuntime.storage .setItems({ [CONSTANTS.TOKEN_STORAGE_KEY]: token, [CONSTANTS.USER_ORGANIZATION]: getDomainFromEmail(username), [CONSTANTS.USER_EMAIL]: username, [CONSTANTS.FLOW_ID]: actualFlowId }); };

Expected behavior

I would expect the stylesheet used by the task pane to download and that the task pane is styled using the styles in the downloaded CSS.

Current behavior

The download https://static2.sharepointonline.com/files/fabric/office-ui-fabric-core/11.0.1/css/fabric.min.css in taskpane.html consistently result in a 404 - Not Found error.

Steps to Reproduce

Please provide detailed steps for reproducing the issue.

1. Use yo office to create a Custom Functions add-in with a task pane
2. Debug in Excel Desktop or Excel Web and open the add-in

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• Operating System:
• Node version:
• Office version:
• Tool version:

Failure Logs

taskpane.html:1

     GET https://static2.sharepointonline.com/files/fabric/office-ui-fabric-core/11.0.1/css/fabric.min.css net::ERR_ABORTED 404