Update dependency lit-html to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
lit-html (source)	1.4.1 -> 3.3.1

---

Release Notes

lit/lit (lit-html)

v3.3.1

Compare Source

Patch Changes

• #​4997 aea85e24 - Update README

• #​4988 6792b7ef Thanks @​ADNolan! - Adjusted the comparison to use the name property of the _$resolve function and the resolveOverrideFn in private ssr support to prevent duplicated patching of the directive class.

• #​4975 43a3f4dc - Remove some redundant code from removePart()

v3.3.0

Compare Source

Minor Changes

• #​4901 c9160405 Thanks @​maxpatiiuk! - Dev mode warnings are now emitted on the next microtask after package import, allowing for a wider opportunity to suppress the warnings by consumers.

Patch Changes

• #​4956 0a9bc720 Thanks @​louis-bompart! - Import barrels explicitly for compatibility with modern Node resolution w/ ESM

v3.2.1

Compare Source

Patch Changes

• #​4782 99703a03 - Revert the Terser plugin for Rollup to rollup-plugin-terser from @rollup/plugin-terser
  due to a bug that prevented our minified name prefixing from working.

v3.2.0

Compare Source

Minor Changes

• #​4637 feccc1ba - Add MathML support with the mathml template tag

v3.1.4

Compare Source

Patch Changes

• #​4646 abf30b3e - The value provided by the ref() directive will always be undefined when the element is disconnected.

v3.1.3

Compare Source

Patch Changes

• #​4570 bd881370 - Fix the lit-html marker length to be consistently 9 characters.

v3.1.2

Compare Source

Patch Changes

• #​4523 1a32b61e - Add a DEV_MODE error to catch duplicate attribute bindings that otherwise create silent errors.

• #​4485 57b00630 - Add "browser" export condition entrypoints to any package.json files with "node"
  export conditions. This fixes Node test runners emulating browser environments that were incorrectly loading the
  "node" entrypoints instead of the browser code.

• #​4515 dca963f7 - Fix a memory leak when patching directive constructors for SSR.

v3.1.1

Compare Source

Patch Changes

• #​4409 1af7991c - asyncReplace correctly re-renders when value is unchanged (#​4408)

v3.1.0

Compare Source

Minor Changes

• #​4309 949a5467 - Adds two new types: UncompiledTemplateResult and MaybeCompiledTemplateResult. Currently UncompiledTemplateResult is the same as TemplateResult, and MaybeCompiledTemplateResult is the union of the compiled and uncompiled types.

v3.0.2

Compare Source

Patch Changes

• #​4345 02b8d620 - Add a dev mode warning if a static value such as literal or unsafeStatic is detected within the non-static html tag function. These should only be used with the static html tag function imported from lit-html/static.js or lit/static-html.js.

v3.0.1

Compare Source

Patch Changes

• #​4240 edf998c9 Thanks @​remziatay! - Improved the type inferece of the choose() directive to properly restrict the case type inferred from provided value. Note: If this change creates a type error in your code, there must have been an unreachable case that can be removed, or the type of your value might be missing a valid case in the union.

• #​4310 8f674ab3 Thanks @​megheaiulian! - The when() directive now calls the case functions with the provided condition value as an argument. This allows the narrowing of types for the condition value based on its truthiness when used as a parameter for the case function.

v3.0.0

Compare Source

Major Changes

• #​3756 f06f7972 - Drop IE11 support

• #​3759 1db01376 - Use replaceWith() for SVG templates

• #​3765 92cedaa2 - Remove experimental hydrate modules. These are available from @lit-labs/ssr-client.

• #​3751 dfd747cf - Simplify lit-html attribute handling for standards-compliant browsers that iterate attributes in source order

• #​3750 c3e473b4 - Use toggleAttribute() to simplify boolean attribute parts

Patch Changes

• #​4141 6b515e43 - Update TypeScript to ~5.2.0

• #​3762 23c404fd - Remove Lit 1 -> Lit 2 migration warnings

v2.8.0

Compare Source

Minor Changes

• #​3993 e2c50569 - Fix return type of isTemplateResult helper to include the CompiledTemplateResult and fix the cache directive to work correctly with CompiledTemplateResults. Also add an explicit isCompiledTemplateResult helper.

v2.7.5

Compare Source

Patch Changes

• #​3968 5bb40831 - Allow undefined to be passed to the ref() directive

• #​3969 7d8d4a15 - Make RefOrCallback generic like Ref

• #​3987 bb2560f1 - Change the h field of CompiledTemplates to a TemplateStringsArray preventing the spoofing of CompiledTemplates by JSON injection attacks. This should not be a breaking change for most users unless you're using CompiledTemplates. This is a necessary security fix, similar to #​2307.

v2.7.4

Compare Source

Patch Changes

• #​3888 0f30e6fb - Fix a memory leak cause by lit-html's shared TreeWalker holding a reference to the last tree it walked.

v2.7.3

Compare Source

Patch Changes

• #​3825 343187b1 - static-html no longer adds an item to TemplateResult's value array for the last consumed static value. This fixes an error with server-side rendering of static html.

• #​3766 4431cbb8 - Fix styleMap initial render of mixed-case custom props

v2.7.2

Compare Source

Patch Changes

• #​3788 88fe0390 - Allow numbers to be used as values in styleMap()

v2.7.1

Compare Source

Patch Changes

• #​3768 7c1191da - Fix styleMap's handling of important flags

• #​3720 575fb578 - lit-html/experimental-hydrate.js and lit-element/experimental-hydrate-support.js have been moved to @lit-labs/ssr-client.

  The modules in the original location have been marked deprecated and will be removed in a future version.

v2.7.0

Compare Source

Minor Changes

• #​3667 e00f6f52 - [SSR only] Improved how nodes with attribute/property/event/element bindings are rendered in SSR, to avoid adding comments inside of "raw text elements" like <textarea>. Fixes #​3663.

  Note: @lit-labs/ssr and lit-html must be updated together.

Patch Changes

• #​3615 4d698430 - Don't throw in ChildPart.parentNode if the parentNode is null

• #​3583 88a40177 - [SSR only] Add more detail to some hydration errors

v2.6.1

Compare Source

Patch Changes

• #​3526 65e56655 - Disable ShadyDOM noPatch in Node dev build. This fixes the issue of throwing due to undefined window.

v2.6.0

Compare Source

Minor Changes

• #​3522 72fcf0d7 - When running in Node, Lit now automatically includes minimal DOM shims which are
  sufficient for most SSR (Server Side Rendering) use-cases, removing the need to
  import the global DOM shim from @lit-labs/ssr.

  The new @lit-labs/ssr-dom-shim package has been introduced, which exports an HTMLElement, CustomElementRegistry, and default customElements singleton.

  The existing @lit-labs/ssr global DOM shim can still be used, and is compatible with the new package, because @lit-labs/ssr imports from @lit-labs/ssr-dom-shim. Importing the global DOM shim adds more APIs to the global object, such as a global HTMLElement, TreeWalker, fetch, and other APIs. It is recommended that users try to remove usage of the @lit-labs/ssr DOM shim, and instead rely on the more minimal, automatic shimming that @lit/reactive-element now provides automatically.

v2.5.0

Compare Source

Minor Changes

• #​3507 b152db29 - lit-html and reactive-element now include development Node builds with unminified code and dev warnings.

v2.4.0

Compare Source

Minor Changes

• #​3318 21313077 - Adds an isServer variable export to lit and lit-html/is-server.js which will be true in Node and false in the browser. This can be used when authoring components to change behavior based on whether or not the component is executing in an SSR context.

v2.3.1

Compare Source

Patch Changes

• #​3223 5a65ca97 - Use existing document in Node build

v2.3.0

Compare Source

Minor Changes

• #​3156 ae6f6808 - Lit and its underlying libraries can now be imported directly from Node without crashing, without the need to load the @​lit-labs/ssr dom-shim library. Note that actually rendering from a Node context still requires the @​lit-labs/ssr dom-shim, and the appropriate integration between @​lit-labs/ssr and your framework/tool.

Patch Changes

• #​3003 daddeb34 - Lit's async-directive now re-exports everything from the directive module.

• #​3199 0725fdb4 - In DEV_MODE, render a warning instead of rendering a template's host in the template.

  Most commonly this would happen when rendering ${this} in a LitElement's template, which has the counterintuitive behavior of removing the element from the DOM, because when rendering the element's template we attach it into its own shadow root, which removes it from the DOM, causing it simply disappear. This is especially problematic with a fast HMR system.

• #​3186 3766ae4c - StaticValue interface type is now exported.

v2.2.7

Compare Source

Patch Changes

• #​3130 1f0567f1 - Export the underlying type of the keyed directive.

• #​3132 2fe2053f - Added "types" entry to package exports. This tells newer versions of TypeScript where to look for typings for each module.

v2.2.6

Compare Source

Patch Changes

• #​2849 b12e8d93 - Expand documentation for render and TemplateResult.

v2.2.5

Compare Source

Patch Changes

• #​2952 a78cc3b7 - Fix SSR hydration bug relating to and other void elements having attribute bindings.

v2.2.4

Compare Source

Patch Changes

• #​2847 79d82385 - Fix typo in API docs for live() directive.

• #​2828 b3b6bc33 - Remove private Lit 2 migration helpers: INTERNAL and clearContainerForLit2MigrationOnly. This logic is no longer depended on.

v2.2.3

Compare Source

Patch Changes

• #​2732 3e181bcb - Enforce use of file extensions in imports. Fixes an issue with older TypeScript compilers.

v2.2.2

Compare Source

Patch Changes

• #​2657 a6069c40 - Remove readonly restriction from StyleInfo interface as addition, deletion, and updating of styles is valid. Expanded styleMap documentation with links to lit.dev.

• #​2642 badc532c - Add an additional security brand check to StaticValues; Similar to #​2307

• #​2691 171143bd - Fixes ref bug when auto-bound class method used as a callback could incorrectly receive undefined.

• #​2661 9a3a38cd - Give a clearer error message when rendering into null/undefined

• #​2646 365cd09a - Clarify that hacking around the template strings array brand error can create security vulnerabilities.

v2.2.1

Compare Source

Patch Changes

• #​2635 ae358703 - Make the event debug logger lazier, doing even less work (with no side effects) even in dev mode unless the page has opted in.

v2.2.0

Compare Source

Minor Changes

• #​2401 2c9d0008 - Added a devlog events system that may be used for debugging and visualizing Lit's internals.

v2.1.3

Compare Source

Patch Changes

• #​2498 2a1dc7a1 - Replace 'rare' with 'invalid' in svg tag function JSDocs.

• #​2459 23df9d45 - Fix bindings inside of <title> elements

• #​2479 89560520 - Expand JSDocs for the svg tagged template literal (TTL). The new documentation makes it more clear that the svg tag function should only be used for SVG fragments, and not for the <svg> HTML element.

v2.1.2

Compare Source

Patch Changes

• #​2399 5ac025bf - Correct typo in async-directive module comment

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

v2.1.1

Compare Source

Patch Changes

• #​2388 5860533f - Fix choose directive jsdoc code example.

v2.1.0

Compare Source

Minor Changes

• #​2337 fcc2b3d0 - Add a keyed(key, value) directive that clears a part if the key changes.

• #​2335 d319cf5f - Add when, map, join, and range directives.

• #​2341 1d563e83 - Add choose() directive

Patch Changes

• #​2307 221cb0a9 - Added an additional check to prevent spoofing of internal lit types in data bindings.

v2.0.2

Compare Source

Patch Changes

• #​2146 8bb33c88 - Work around a Chrome bug with trusted types: https://crbug.com/993268

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

v2.0.1

Compare Source

Patch Changes

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

v2.0.0

Compare Source

Major Changes

• The templateFactory option of RenderOptions has been removed.

• TemplateProcessor has been removed.

• Symbols are not converted to a string before mutating DOM, so passing a Symbol to an attribute or text binding will result in an exception.

• The shady-render module has been removed and is now part of platform-support, and Lit's polyfill support now adds the following limitations: (1) Bindings in style elements are no longer supported. Previously these could not change and in the future they may be supported via static bindings. (2) ShadyCSS.styleElement is no longer called automatically. This must be called whenever dynamic changes that affect styling are made that involve css custom property shimming (older browsers) or changes to custom properties used via the deprecated @apply feature. It was previously called only on first render, and it is now up to the user to decide when this should be called. See Polyfills for more details.

• render() no longer clears the container it's rendered to. It now appends to the container by default.

• Expressions in comments are no longer rendered or updated. See Valid expression locations for more details.

• Template caching happens per callsite, not per template-tag/callsize pair. This means some rare forms of highly dynamic template tags are no longer supported.

• Arrays and other iterables passed to attribute bindings are not specially handled. Arrays will be rendered with their default toString representation. This means that html`<div class=${['a', 'b']}> will render <div class="a,b"> instead of <div class="a b">. To get the old behavior, use array.join(' ').

• Multiple bindings in a single attribute value don't require the attribute value is quoted, as long as there is no whitespace or other attribute-ending character in the attribute value. html`<div id=${a}-${b}>`

• The directive and part APIs are significantly different. See Custom Directives and the Upgrade Guide for more details.

• The Directive base class and directive() factory function are
  now exported from the lit-html/directive.js module.

• NodePart has been renamed to ChildPart,
  along with other methods and variables that use the "Node" naming, like
  PartType.Node which is now PartType.CHILD.

• The part exports (ChildPart,
  AttributePart, etc) have been change to interface-only exports. The constructors are no longer exported. Directive authors should use helpers in directive-helpers.js to construct parts.

• The eventContext render option has been changed to host.

• #​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.

• #​1764 0b4d6eda - Don't allow classMap to remove static classes. This keeps classMap consistent with building a string out of the classnames to be applied.

Minor Changes

• Added renderBefore to render options. If specified, content is rendered before the node given via render options, e.g. {renderBefore: node}.
• Added development mode, which can be enabled by setting the development Node exports condition. See Development and production builds for more details.
• All usage of instanceof has been removed, making rendering more likely to
  work when multiple instances of the library interact.
• Template processing is more robust to expressions in places other than text and attribute values.
• render now returns the ChildPart that was created/updated by render.
• Added AsyncDirective, which is a Directive subclass whose
  disconnected callback will be called when the part containing the directive
  is cleared (or transitively cleared by a Part higher in the tree) or manually
  disconnected using the setConnected API, and whose reconnected callback
  will be called when manually re-connected using setConnected. When
  implementing disconnected, the reconnected callback should also be
  implemented to return the directive to a usable state. Note that LitElement
  will disconnect directives upon element disconnection, and re-connect
  directives upon element re-connection. See Async directives for more details.
• Added setConnected(isConnected: boolean) to ChildPart; when called with
  false, the disconnected callback will be run on any directives contained within
  the part (directly or transitively), but without clearing or causing a
  re-render to the tree. When called with true, any such directives'
  reconnected callback will be called prior to its next update/render
  callbacks. Note that LitElement will call this method by default on the
  rendered part in its connectedCallback and disconnectedCallback.
• Added the static-html module, a static html tag function, a literal tag function, and unsafeStatic(), which allows template authors to add strings to the
  static structure of the template, before it's parsed as HTML. See Static expressions for more details.
• Added lit-html/directive-helpers.js module with helpers for creating custom directives. See Custom directives for more details.
• Rendering null, undefined, or empty string in a ChildPart now has the same affect as rendering nothing: it does not produce an empty text node. When rendering into an element with Shadow DOM, this makes it harder to inadvertently prevent <slot> fallback content from rendering.
• Nested directives whose parent returns noChange are now unchanged. This
  allows the guard directive to guard directive values (#​1519).
• Added optional creationScope to RenderOptions, which controls the node from which the template is cloned from.
• Added support for running with Trusted Types enforced.

Patch Changes

• #​1922 8189f094 - Binding noChange into an interpolated attribute expression now no longer removes the attribute on first render - instead it acts like an empty string. This is mostly noticable when using until() without a fallback in interpolated attributes.

• #​1964 f43b811 - Don't publish src/ to npm.

• #​2070 a48f39c8 - Throw instead of rendering an innocuous value into a style or script when security hooks are enabled.

• #​2044 662209c3 - Improves disconnection handling for first-party AsyncDirectives (until, asyncAppend, asyncReplace) so that the directive (and any DOM associated with it) can be garbage collected before any promises they are awaiting resolve.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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, check this box

---

This PR was generated by Mend Renovate. View the repository job log.