Title: TypeError: n[e] is not a function
Last modified: March 24, 2026

---

# TypeError: n[e] is not a function

 *  Resolved [thedenizen](https://wordpress.org/support/users/thedenizen/)
 * (@thedenizen)
 * [2 months, 3 weeks ago](https://wordpress.org/support/topic/typeerror-ne-is-not-a-function/)
 * **TypeError: n[e] is not a function**
 * I am getting error on Woocommerce version 10.6.1 Google for Woocommerce version
   3.6.0
   and wordpress version 6.9.4
 * i tried with health check and it also does the same with Default theme + all 
   plugins disabled except for woocommerce + google for woocommerce.
 * here is the error in console [https://snipboard.io/6YLVz5.jpg](https://snipboard.io/6YLVz5.jpg)
   
   It happens when i go to wp-admin/admin.php?page=wc-admin&path=%2Fgoogle%2Fsetup-
   mcto setup merchant center, it was already set-up but now i am getting error 
   opening this page.After uninstalling and clearing the data i can not relink it
   and i am still getting the same type error.So even after all that health check
   still does not let me open that page on default theme 2025 + only woocommerce
   + google for woocommerce.Can someone help me, could this be related to the latest
   updates? rollbacking hasnt worked either

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Support [Frank Remmy (woo-hc)](https://wordpress.org/support/users/frankremmy/)
 * (@frankremmy)
 * [2 months, 3 weeks ago](https://wordpress.org/support/topic/typeerror-ne-is-not-a-function/#post-18861669)
 * Hi [@thedenizen](https://wordpress.org/support/users/thedenizen/),
 * Thanks for the detailed report and for already running through health check.
 * I see the issue is related to Google for WooCommerce, so I would recommend [opening a thread](https://wordpress.org/support/plugin/google-listings-and-ads/#new-topic-0)
   on its support forum. I know it’s a hassle having to post in the wrong channel
   the second time, so I’ll go ahead and explain what’s happening so you can reply
   in the right forum.
 * Looking at the console error in your screenshot, the crash is happening inside`
   @wordpress/data`‘s internal store subscription machinery, triggered by Google
   for WooCommerce’s `settings.js` when the Merchant Center setup page loads. The
   error pattern suggests a JS package version mismatch, specifically, the way Google
   for WooCommerce’s settings script is interacting with the `@wordpress/data` store
   registry appears incompatible with what WooCommerce 10.6.1 currently ships with.
   This would explain why it persists even with only those two plugins active.
 * Before we dig deeper, could you try a couple of things:
    1. Hard clear your browser cache. Not just a normal refresh, but a full cache wipe(
       in Chrome: Settings → Clear browsing data → Cached images and files). Then try
       loading the Merchant Center setup page again. This rules out a stale `commons.
       js` being served from cache, which can cause exactly this type of mismatch.
    2. Try in a different browser (Firefox, Edge, etc.) with no extensions (or incognito)
       just to confirm whether it’s browser/cache specific.
    3. Share your System Status Report at WooCommerce → Status → Get system report,
       pasted at [https://gist.github.com](https://gist.github.com). Particularly interested
       in your PHP version, server environment, and any other active plugins.
 * I hope that helps. I’ll go ahead and close this thread, but please let us know
   how the cache clear goes in the new thread! Be sure to add a link to this one.
 *  Thread Starter [thedenizen](https://wordpress.org/support/users/thedenizen/)
 * (@thedenizen)
 * [2 months, 3 weeks ago](https://wordpress.org/support/topic/typeerror-ne-is-not-a-function/#post-18861683)
 * Hi frank sorry for posting in the wrong threads, ive been panicking because off
   the issues with the product feed that have occured because of my stupidity in
   trying to fix it even though it was technically still working.
   This is the thread:
   [https://wordpress.org/support/topic/typeerror-ne-is-not-a-function-2/](https://wordpress.org/support/topic/typeerror-ne-is-not-a-function-2/)
 *  Plugin Support [Frank Remmy (woo-hc)](https://wordpress.org/support/users/frankremmy/)
 * (@frankremmy)
 * [2 months, 3 weeks ago](https://wordpress.org/support/topic/typeerror-ne-is-not-a-function/#post-18861733)
 * No worries [@thedenizen](https://wordpress.org/support/users/thedenizen/)!
 * That happens and we completely understand. We’ll continue troubleshooting in 
   the other thread.
 * Take care.

Viewing 3 replies - 1 through 3 (of 3 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ftypeerror-ne-is-not-a-function%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/woocommerce/assets/icon.svg?rev=3234504)
 * [WooCommerce](https://wordpress.org/plugins/woocommerce/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/woocommerce/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/woocommerce/)
 * [Active Topics](https://wordpress.org/support/plugin/woocommerce/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/woocommerce/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/woocommerce/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [Frank Remmy (woo-hc)](https://wordpress.org/support/users/frankremmy/)
 * Last activity: [2 months, 3 weeks ago](https://wordpress.org/support/topic/typeerror-ne-is-not-a-function/#post-18861733)
 * Status: resolved