v7.2.0 (2018-11-27)

• Angular v7.1.0+
• Add ElementsLoaderService.registerContainingCustomElements() method to be used for AoT compiler
• ElementsLoaderService.loadContainingCustomElements() method must be used only for JiT compiler
• Explain how to create an optimized webcomponent bundle with this tutorial
• Documentation

v7.1.0 (2018-11-09)

• Angular v7.0.3+
• document-register-elements v1.13.1 latest version of the polyfill only require if your browser doesn't support customElement
• @webcomponents/webcomponentsjs v2.1.3 to fix issue with es5 compilation outside Angular application like explain here
• Allow custom elements registration in browser even if tag isn't yet present in the DOM like this, it can be created or loaded asynchronously after registration
• Documentation

v7.0.0 (2018-11-02)

• Angular v7.0.2+
• Documentation

v6.4.2 (2018-10-18)

• Angular v6.1.10+
• Explain how to add new polyfills for reflect api to solve bug reported in this issue
• Provide ElementsLoaderService in ElementsLoaderModule to solve bug reported in this issue
• Documentation

v6.4.1 (2018-09-27)

• Fix version to Angular v6.1.7 to avoid the bug reported in this issue
• Documentation

v6.4.0 (2018-07-26)

• Angular v6.1.0+
• Documentation

v6.3.2 (2018-07-19)

• Latest packages' versions
• Documentation
• Delete ng-shadow-dom-renderer project

v6.3.1 (2018-06-20)

• Delete ShadowDomV1Renderer factory in @hapiness/custom-elements-loader because not compatible with multi-components

v6.3.0 (2018-06-20)

• Create @hapiness/ng-shadow-dom-renderer package
• Use ShadowDomV1Renderer factory from @hapiness/ng-shadow-dom-renderer in @hapiness/custom-elements-loader to fix angular issue #24397
• Latest packages' versions
• Documentation

v6.1.1 (2018-06-12)

• Downgrade document-register-element to v1.8.1 to fix angular issue #24390
• Latest packages' versions
• Documentation