You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m reaching out for guidance on an issue I’ve encountered while running Excel add-in unit tests using office-addin-mock. My test suite attempts to execute these tests in the browser, as that’s where my add-in functions are executed. However, I’m encountering Node-related dependency errors that aren’t resolved even with vite-plugin-node-polyfills.
Could you clarify why office-addin-mock requires Node.js dependencies, particularly for objects in the browser environment? After reviewing the library, it appears that much of the Node dependency originates from office-addin-usage-data, which is required by office-addin-mock. If this dependency—and its associated data collection functionality—are essential, it imposes a significant restriction on running these tests purely in the browser. This limitation creates an unsatisfactory experience for developers attempting to conduct browser-based testing for Office add-ins.
Any insights on this matter would be greatly appreciated, as this dependency affects the overall user experience and ease of development within the Office add-in ecosystem.
Thank you for your time and attention.
The text was updated successfully, but these errors were encountered:
I’m reaching out for guidance on an issue I’ve encountered while running Excel add-in unit tests using office-addin-mock. My test suite attempts to execute these tests in the browser, as that’s where my add-in functions are executed. However, I’m encountering Node-related dependency errors that aren’t resolved even with vite-plugin-node-polyfills.
Could you clarify why office-addin-mock requires Node.js dependencies, particularly for objects in the browser environment? After reviewing the library, it appears that much of the Node dependency originates from office-addin-usage-data, which is required by office-addin-mock. If this dependency—and its associated data collection functionality—are essential, it imposes a significant restriction on running these tests purely in the browser. This limitation creates an unsatisfactory experience for developers attempting to conduct browser-based testing for Office add-ins.
Any insights on this matter would be greatly appreciated, as this dependency affects the overall user experience and ease of development within the Office add-in ecosystem.
Thank you for your time and attention.
The text was updated successfully, but these errors were encountered: