-
Notifications
You must be signed in to change notification settings - Fork 880
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
Version Packages #4399
Merged
Merged
Version Packages #4399
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
November 16, 2023 00:11
2b9c3d1
to
409316e
Compare
📊 Tachometer Benchmark ResultsSummarynop-update
render
update
update-reflect
Resultsthis-change
render
update
update-reflect
this-change, tip-of-tree, previous-release
render
update
nop-update
this-change, tip-of-tree, previous-release
render
update
this-change, tip-of-tree, previous-release
render
update
update-reflect
|
augustjk
approved these changes
Nov 16, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
The size of lit-html.js and lit-core.min.js are as expected. |
the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@lit/context@1.1.0
Minor Changes
62df19da
Thanks @autopulated! -ContextProvider
can now be added to any HTML elements, not just custom elements implementing aReactiveControllerHost
.Patch Changes
22919f6d
- Make property decorated with@provide()
with TypeScript experimental decorators configurable. This allows chaining additional decorators that modify the property like@property()
fromlit
.@lit-labs/ssr@3.2.0
Minor Changes
011b762d
- Add a server-only html function, to define templates that will only be rendered on the server.Patch Changes
#4389
ef2976b9
- Fix a race condition inRenderResultReadable
which could skip async work.Updated dependencies [
bf551b5b
,949a5467
,c7922a0c
,839ca0f8
]:lit@3.1.0
Minor Changes
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.Patch Changes
#4387
bf551b5b
- EnsurerenderRoot
exists before first update (ReactiveElement: callingperformUpdate
before an element is in the DOM causes exception #4268)#4282
c7922a0c
Thanks @MaxArt2501! - Fix a bug where accessing a@query
decorated field with thecache
flag set before the first update would result innull
being cached permanently.null
will no longer be cached before the first update and inDEV_MODE
now raises a warning.#4388
839ca0f8
- Fixes bug where adding or removing controllers during a reactive controller lifecycle would affect the execution of other controllers (ReactiveController: adding/removing controllers in lifecycle methods affects other controllers #4266). Controllers can now be added/removed during lifecycle without affecting others.Updated dependencies [
949a5467
]:lit-html@3.1.0
Minor Changes
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.@lit-labs/nextjs@0.1.4
Patch Changes
c8e1509c
- Add plugin optionaddDeclarativeShadowDomPolyfill
which, if true, will add a script to the client bundle which will apply the@webcomponents/template-shadowroot
ponyfill on the document. Note: If you were manually adding the polyfill, you can either remove your own implementation or set this option tofalse
.@lit-labs/ssr-react@0.2.3
Patch Changes
#4364
1ea4720f
- Fix rendering of nested custom elements so that child custom elements will properly have thedefer-hydration
attribute from SSR, ensuring correct hydration order from parent to child.Updated dependencies [
ef2976b9
,011b762d
]:@lit-labs/virtualizer@2.0.11
Patch Changes
#4375
449bc281
Thanks @graynorton! - Fix issue where virtualizer didn't render children when slotted into a position:fixed ancestor ([labs/virtualizer] offsetParent issue report – virtualizer not working #4346)Updated dependencies [
bf551b5b
,949a5467
,c7922a0c
,839ca0f8
]:lit-element@4.0.2
Patch Changes
#4387
bf551b5b
- EnsurerenderRoot
exists before first update (ReactiveElement: callingperformUpdate
before an element is in the DOM causes exception #4268)#4282
c7922a0c
Thanks @MaxArt2501! - Fix a bug where accessing a@query
decorated field with thecache
flag set before the first update would result innull
being cached permanently.null
will no longer be cached before the first update and inDEV_MODE
now raises a warning.#4388
839ca0f8
- Fixes bug where adding or removing controllers during a reactive controller lifecycle would affect the execution of other controllers (ReactiveController: adding/removing controllers in lifecycle methods affects other controllers #4266). Controllers can now be added/removed during lifecycle without affecting others.Updated dependencies [
949a5467
]:@lit/react@1.0.2
Patch Changes
001a1b78
- Prefer type of property from an element over built-in React HTMLAttribute types. This also fixes type errors that would arise when they collide and can't be intersected.@lit/reactive-element@2.0.2
Patch Changes
#4387
bf551b5b
- EnsurerenderRoot
exists before first update (ReactiveElement: callingperformUpdate
before an element is in the DOM causes exception #4268)#4282
c7922a0c
Thanks @MaxArt2501! - Fix a bug where accessing a@query
decorated field with thecache
flag set before the first update would result innull
being cached permanently.null
will no longer be cached before the first update and inDEV_MODE
now raises a warning.#4388
839ca0f8
- Fixes bug where adding or removing controllers during a reactive controller lifecycle would affect the execution of other controllers (ReactiveController: adding/removing controllers in lifecycle methods affects other controllers #4266). Controllers can now be added/removed during lifecycle without affecting others.@lit-internal/test-elements-react@1.0.3
Patch Changes
001a1b78
]: