Bump lit-html from 1.4.1 to 2.0.1

[dependabot[bot]]

Bumps lit-html from 1.4.1 to 2.0.1.

Release notes

Sourced from lit-html's releases.

lit-html@2.0.1

Patch Changes

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

lit-html@2.0.0

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

... (truncated)

Changelog

Sourced from lit-html's changelog.

2.0.1

Patch Changes

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

2.0.0

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.

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

Looks like lit-html is up-to-date now, so this is no longer needed.