prettier-config | Prettier rules | Code Quality library

It is not currently possible to disable that specific rule from prettier through configuration, but to override rules in eslint that come from the extends block, you can either write in the rule like this:

Thanks to discussion https://github.com/open-wc/open-wc/issues/730 I reached the solution:

I have to do two things in order to unit test my vanilla webcomponent spplited in two files:

my webcomponent javascript

Based on those dependencies, I'm assuming your add-in project was created by yo office.

Updating those dev dependencies (via npm install) will only affect the development experience and not the runtime of the add-in. The main benefit to updating the types dependencies will be as new APIs are added, you will be able to call them from TypeScript code. And if you use the manifest validation functionality provided by yo office, updating the dependencies will include any updates to the manifest schema used for validation.

The linked documentation refers to two updates that you won't need to do because the add-in created by yo office already uses manifest schema version 1.1. In particular, so long as Office.js is loaded from the CDN location, your add-in will always use the latest version of the Office.js API.