@open-wc/scoped-elements
Advanced tools
Comparing version 2.0.0-next.6 to 2.0.1
# Change Log | ||
## 2.0.1 | ||
### Patch Changes | ||
- 1649ba46: Release bump version as major versions have already been used and unpublished in an accidental publish about a year ago. | ||
## 2.0.0 | ||
### Major Changes | ||
- edca5a82: Adds compatibility for [lit](https://lit.dev/) with `lit-html v2` and `lit-element v3`. | ||
- This version does NOT work with lit-element v2 - please use Scoped Elements v1 for it | ||
- Uses a `CustomElementsRegistry` instance for each component class instead of for each component instance. In case you need to have a registry for each component instance, you must override the registry `get` and `set` methods to bind the registry to the component instance | ||
```js | ||
/** @override */ | ||
get registry() { | ||
return this.__registry; | ||
} | ||
/** @override */ | ||
set registry(registry) { | ||
this.__registry = registry; | ||
} | ||
``` | ||
- `getScopedTagName` became deprecated - use the native `el.tagName` instead | ||
### Minor Changes | ||
- 1e54d297: Use the webcomponents polyfill instead of the forked one | ||
### Patch Changes | ||
- 4b9ea6f6: Use lit@2.0 stable based dependencies across the project. | ||
- c05d92fb: Mark `loadPolyfill.js` as a side effect | ||
- 0513917c: Keep deprecated static getScopedTagName function | ||
- ff17798f: Adjust the renderBefore node so that any styles in Lit content render before adoptedStyleSheets. | ||
- a0b5e360: fix getScopedTagName returning the tag that was passed in | ||
## 2.0.0-next.6 | ||
@@ -4,0 +45,0 @@ |
{ | ||
"name": "@open-wc/scoped-elements", | ||
"version": "2.0.0-next.6", | ||
"version": "2.0.1", | ||
"publishConfig": { | ||
@@ -17,2 +17,3 @@ "access": "public" | ||
"module": "index.js", | ||
"type": "module", | ||
"scripts": { | ||
@@ -19,0 +20,0 @@ "debug": "cd ../../ && yarn debug --group scoped-elements", |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
No v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
53990
0
Yes