@lwc/module-resolver

Improvements

• deprecated

  #1395 - engine: A Lightning web component class can be used to register a custom element in the registry. This change introduces a new way to access the class constructor. This change also soft deprecates the previous method of creating the constructor.

class MyComponent extends LightningElement {
}

customElements.define('my-component', MyComponent.CustomElementConstructor);

• #1459, #1823 - wire-service: Decouples the wire service from the LWC engine and implements the underlying reactive tracking for wired configuration and wired methods using the same reactivity system as LWC. See all the details in the wire reform decorator RFC.

Breaking changes

• Current wire adapterIds defined as Symbol will be broken with this update.
  Upgrade path to LWC v1.5.0:

export const adapterId = Symbol('AdapterId');

// should change to:

export const adapterId = () => {
    throw new Error("Imperative use is not supported. Use @wire(adapterId)");
}; 

Bug Fixes

• #1793 - synthetic-shadow: Fixed an issue where invoking Node.prototype.contains() on the same node was returning false.

• #1794 - engine: Fixed an issue where slotted content became invisible during a subsequent re-rendering of the slot receiver.

• #1819 - integration-karma: Disabled two test cases related to AOM property reflection due to browser bugs.

Internal

• #1786 - (synthetic-shadow): Reverts #1754

• #1796, #1825 : Routine dependency updates.

• #1828 - engine: When a component class has been marked to have a circular reference, use the constructor after resolving the circular reference.

Security

• security

  #1804: Fixed security advisory CVE-2020-7598.