Issues with mandatory Jetpack activation for taxes in local development env.

Hello,

I hope this message finds you well. I’m currently facing an issue related to the recent changes in the WooCommerce setup, specifically regarding the mandatory use of Jetpack for taxes.

While I understand the benefits of integrating Jetpack for tax calculations, this requirement presents a significant challenge in a local development environment. As you may know, Jetpack needs to be activated, which requires a live site to connect to WordPress.com. This is not always feasible in a local development setting.

This change has created a hurdle in the development process, as it’s not always practical or desirable to have Jetpack active in a local environment. It’s crucial for developers to have the ability to work and test all aspects of a WooCommerce store, including taxes, in a local environment before pushing changes to a live site.

I kindly request the WooCommerce team to consider providing an alternative solution or workaround for this issue. Perhaps a way to bypass the Jetpack activation requirement for taxes in local development environments, or a method to simulate Jetpack’s tax features locally, could be potential solutions.

I believe this would greatly benefit the WooCommerce developer community and improve the overall development process. I’m sure many other developers are facing similar challenges, and a solution to this issue would be greatly appreciated.

Thank you for your time and consideration. I look forward to hearing your thoughts on this matter.

Best regards,
Fadi