Using js-meta tag feature breaks the LWC extension activation

[lcampos]

Summary

From thread on #2862
The LWC extension fails to activate when using it next to the the Red Hat extension.

Failed to setup Red Hat XML extension

Cannot read property 'addXMLCatalogs' of undefined
This seems to relate to this line.

Just to add what doesn't work:

• No intellisense in markup (i. e. class field lookup within expression)
• No commands in the command palette available for interaction with LWC Local Dev Server

And for example this works:

• LWC Test commands in command palette
• LWC compiler validation (i. e. throwing LSP errors on invalid LWC syntax)
• GoToDefinition from markup into JS
  It looks a bit like some part of the LSP work, and others not.

Steps To Reproduce:

1. Setup js-meta feature on LWC https://developer.salesforce.com/tools/vscode/en/lwc/writing/#supporting-js-metaxml
2. Open a Salesforce project

Additional information

This is the line causing the problem. More details at #2862

[git2gus]

This issue has been linked to a new work item: W-8852786

[lcampos]

Closing this since we released a fix that prevents errors in RedHat XML from affecting the LWC extension activation. If you want to use the js-meta feature you should use version 0.14.0 of the RedHat XML extension (for now).