Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency lit-element to v3 #118

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jan 28, 2022

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
lit-element (source) ^2.5.1 -> ^3.1.2 age adoption passing confidence

Release Notes

lit/lit

v3.1.2

Compare Source

Patch Changes
  • #​2370 7453e365 - Replace square bracket links with the linkcode JSDoc tag.
    Editors will create a jump to definition hyperlink for the linkcode tag if the identifier is in scope.

  • #​2410 b9a6962b - Correct the link path of CONTRIBUTING.md in README.md files

v3.1.1

Compare Source

Patch Changes

v3.1.0

Compare Source

Minor Changes
  • #​2327 49ecf623 - Add queryAssignedElements decorator for a declarative API that calls HTMLSlotElement.assignedElements() on a specified slot. selector option allows filtering returned elements with a CSS selector.
Patch Changes

v3.0.2

Compare Source

Patch Changes
  • #​2236 5fc3818a - Prevent polyfillSupport.noPatchSupported from implicitly being any.
    Deduplicate types for DevMode-suffixed polyfill support functions.

v3.0.1

Compare Source

Patch Changes
  • #​2152 ba5e1391 - Replace dynamic name lookups for polyfill support functions with static names.

v3.0.0

Compare Source

Major Changes
  • Most users should no longer import directly from lit-element, and instead prefer importing LitElement from the lit packages. The default entry point for lit-element remains backward-compatible and includes all decorators. However, it's recommended to use import {LitElement} from 'lit'; and import decorators from lit/decorators as necessary. See the Upgrade Guide for more details.

  • UpdatingElement has been moved from the lit-element package to the @lit/reactive-element package and renamed to ReactiveElement. See the ReactiveElement API documentation for more details. In addition, the source for css-tag, and all decorators have been moved to @lit/reactive-element. However, all symbols are re-exported from both lit and lit-element packages.

  • The @internalProperty decorator has been renamed to @state.

  • Errors that occur during the update cycle were previously squelched to allow subsequent updates to proceed normally. Now errors are re-fired asynchronously so they can be detected. Errors can be observed via an unhandledrejection event handler on window.

  • The lib folder has been removed.

  • Rendering of renderRoot/shadowRoot) via createRenderRoot and support for static styles has moved from LitElement to ReactiveElement.

  • The createRenderRoot method is now called just before the first update rather than in the constructor. Element code can not assume the renderRoot exists before the element hasUpdated. This change was made for compatibility with SSR.

  • ReactiveElement's initialize method has been removed. This work is now done in the element constructor.

  • The static render has been removed.

  • For consistency, renamed _getUpdateComplete to getUpdateComplete.

  • When a property declaration is reflect: true and its toAttribute function returns undefined the attribute is now removed where previously it was left unchanged (#​872).

  • The dirty check in attributeChangedCallback has been removed. While technically breaking, in practice it should very rarely be (#​699).

  • LitElement's adoptStyles method has been removed. Styling is now adopted in createRenderRoot. This method may be overridden to customize this behavior.

  • LitElement's static getStyles method has been renamed to static finalizeStyles and now takes a list of styles the user provided and returns the styles which should be used in the element. If this method is overridden to integrate into a style management system, typically the super implementation should be called.

  • Removed build support for TypeScript 3.4.

  • Decorators are no longer exported from the lit-element module. Instead, import any decorators you use from lit/decorators/*.

  • lit-html has been updated to 2.x.

  • Support for running in older browsers has been removed from the default configuration. Import the polyfill-support module to support Shady DOM. Note also that Lit parts inside <style> elements are no longer supported. See Polyfills for more details.

  • For simplicity, requestUpdate no longer returns a Promise. Instead await the updateComplete Promise.

  • Removed requestUpdateInternal. The requestUpdate method is now identical to this method and should be used instead.

  • #​2103 15a8356d - Updates the exports field of package.json files to replace the subpath
    folder
    mapping

    syntax with an explicit list of all exported files.

    The /-suffixed syntax for subpath folder mapping originally used in these
    files is deprecated. Rather than update to the new syntax, this change replaces
    these mappings with individual entries for all exported files so that (a) users
    must import using extensions and (b) bundlers or other tools that don't resolve
    subpath folder mapping exactly as Node.js does won't break these packages'
    expectations around how they're imported.

Minor Changes
  • A public renderOptions class field now exists on LitElement and can be set/overridden to modify the options passed to lit-html.
  • Adds static shadowRootOptions for customizing shadowRoot options. Rather than implementing createRenderRoot, this property can be set. For example, to create a closed shadowRoot using delegates focus: static shadowRootOptions = {mode: 'closed', delegatesFocus: true}.
  • Adds development mode, which can be enabled by setting the development Node exports condition. See Development and production builds for more details.
Patch Changes

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot requested a review from a team as a code owner January 28, 2022 02:37
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@renovate
Copy link
Author

renovate bot commented Jan 28, 2022

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 3.x releases. However, if you upgrade to 3.x manually then Renovate will reenable minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants