We've moved discussions to Discord

Trix error: Uncaught DOMException ... (in my local Dev environment; not a deployment issue)

Jeff Helman
Uncaught DOMException: Failed to execute 'define' on 'CustomElementRegistry': the name "trix-toolbar" has already been used with this registry

Does this ring any bells?

I'm not doing anything with this functionality, so it appears that I have a configuration collision somewhere.  Here is what I see for configuration breadcrumbs:
I'm guessing this would NOT be a CSS issue, but ...

... and:

Yarn vs. NPM collision?

I do recall seeing a Yarn warning message which says something about what is in my Yarn.lock file vs. package-lock.json (I believe ...). If this is the root cause, how do I fix that?

Thanks in advance for any help.

Jeff Helman
Thanks  Chris Oliver !  I tried that (in all the .js's), but I'm getting the same result. This is a "silent" failure behind the scenes (in Chrome Dev Tools console), and I'm not using the Trix functionality at the moment, so I will ignore this for now.

Thanks again!
Notifications
You’re not receiving notifications from this thread.