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 #3160
Closed
Closed
Version Packages #3160
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
📊 Tachometer Benchmark ResultsSummarynop-update
render
update
update-reflect
Resultslit-element-list
render
update
update-reflect
lit-html-kitchen-sink
render
update
nop-update
lit-html-repeat
render
update
lit-html-template-heavy
render
update
reactive-element-list
render
update
update-reflect
|
closing to fix changeset formatting for |
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-labs/analyzer@0.2.2
Patch Changes
7d185b4e
- Upgraded TypeScript version to ~4.7.4@lit-labs/context@0.1.3
Patch Changes
2fe2053f
- Added "types" entry to package exports. This tells newer versions of TypeScript where to look for typings for each module.@lit-labs/motion@1.0.3
Patch Changes
2fe2053f
- Added "types" entry to package exports. This tells newer versions of TypeScript where to look for typings for each module.@lit-labs/observers@1.0.2
Patch Changes
2fe2053f
- Added "types" entry to package exports. This tells newer versions of TypeScript where to look for typings for each module.@lit-labs/react@1.0.7
Patch Changes
#3072
94722633
- Avoid nested component props type declarations. Incrementally define what types are needed rather than nesting.#3067
f3e3cddf
- Fixed an error that occurs when when compiling TS. The error occurs when createComponent() is not provided an event map causing instance properties to be confused with event handlers.#3111
6158482c
- Removed the unexposed and unnecessaryStringValued
type used to correlate property names with event listener names.#3132
2fe2053f
- Added "types" entry to package exports. This tells newer versions of TypeScript where to look for typings for each module.@lit-labs/scoped-registry-mixin@1.0.1
Patch Changes
2fe2053f
- Added "types" entry to package exports. This tells newer versions of TypeScript where to look for typings for each module.@lit-labs/ssr@2.2.2
Patch Changes
#3138
6450e17b
- JS source maps now include the TS source inline#3136
afff4c17
- Upgrade node-fetch version@lit-labs/task@1.1.3
Patch Changes
#3131
ec87d529
- Update Task typings to work better with inference and casting args toas const
by making args a readonly array.#3132
2fe2053f
- Added "types" entry to package exports. This tells newer versions of TypeScript where to look for typings for each module.@lit-labs/virtualizer@0.7.1
Patch Changes
#3136
afff4c17
- Upgrade tslib version#3136
afff4c17
- Upgrade event-target-shim#3133
36db238c
- The virtualize directive will now correctly re-render children when data stored outside the items array has changed.Changed
The
scroll
directive has been renamed tovirtualize
. Note that the<lit-virtualizer>
element remains the recommended way to use virtualizer in most cases; the directive exists primarily for developers who are using Lit'slit-html
templating system standalone and don't need theLitElement
base class elsewhere in their project.By default, a virtualizer instance is no longer itself a scroller; rather, it is a block-level container that:
If you want to make a
<lit-virtualizer>
element into a scroller, you can do so by adding thescroller
attribute; likewise, you can setscroller: true
if you're using thevirtualize
directive.As a result of this change, the
scrollTarget
property / attribute is no longer needed and has been removed.In
0.5
and0.6
, it was necessary to explicitly specify a layout. In0.7
, we revert to the behavior from earlier versions: if you don't specify a layout, the default layout (previously calledLayout1d
, now calledflow
—see below) will be used (and loaded dynamically as needed).The lineup of layouts has been updated and cleaned up. The default layout, previously called
Layout1d
, is now calledflow
. The previous, rudimentary grid layouts have been replaced with a single, newgrid
layout with some options to control its behavior. TheLayout1dFlex
layout has been renamed toflexWrap
and remains a work in progress, not yet fully usable (though getting close).The syntax for specifying layouts has changed; rather than providing a layout constructor (e.g.,
FlowLayout
) or a configuration object containing the required type property (e.g.{type: FlowLayout, direction: ‘horizontal’}
), you now import a layout as a function and call that function (passing it an optional configuration object as desired). For example:The
spacing
property of the default layout (which has been present since the earliest releases but never documented) has been removed. Setting margins on the child elements you render is the way to control spacing. This margin-based method was already supported and recommended / demonstrated in previous versions, but has been improved in0.7
with basic support for margin-collapsing: margins set explicitly on child elements will now be collapsed, but any margins on elements contained within child elements are not considered. If you were relying on the previous (non-collapsing) behavior, you may need to adjust existing style rules.In another return to pre-
0.5
behavior, thevisibilityChanged
andrangeChanged
events are no longerCustomEvent
s, so you’ll access their properties directly from the event object, not from under adetails
property. Additionally, these event objects no longer contain both range and visibility information; rather,visibilityChanged
reports only visibility changes andrangeChanged
reports only range changes. Both event objects have just two properties:first
andlast
.Inline API docs are still minimal, but types for
<lit-virtualizer>
, thevirtualize
directive and the various layouts are essentially correct and complete, so typeahead / autocomplete should work if your editor has these features.Exports from the
@lit-labs/virtualizer
packaged are now restricted by an export map. If you have been importing from any modules not intended to be part of the current public API (or if we have inadvertently left something out of the map), things may break—please file issues as needed.The LitVirtualizer class has been extracted into a separate file (
LitVirtualizer.js
) so that, if necessary, it can be imported without registering the<lit-virtualizer>
custom element as a side effect.Fixed
renderItem()
function (#109)The following are also believed to be fixed, but didn't have specific repro cases to test against so require confirmation:
window
not removed (#55)items
array changes (#108)lit@2.2.8
Patch Changes
#3130
1f0567f1
- Export the underlying type of thekeyed
directive.#3132
2fe2053f
- Added "types" entry to package exports. This tells newer versions of TypeScript where to look for typings for each module.lit-element@3.2.2
Patch Changes
2fe2053f
- Added "types" entry to package exports. This tells newer versions of TypeScript where to look for typings for each module.lit-html@2.2.7
Patch Changes
#3130
1f0567f1
- Export the underlying type of thekeyed
directive.#3132
2fe2053f
- Added "types" entry to package exports. This tells newer versions of TypeScript where to look for typings for each module.@lit/localize-tools@0.6.5
Patch Changes
#3116
7d185b4e
- Upgraded TypeScript version to ~4.7.4#3136
afff4c17
- Updated xmldom dependency. Minor change to XML attribute formatting can be expected.@lit/reactive-element@1.3.4
Patch Changes
2fe2053f
- Added "types" entry to package exports. This tells newer versions of TypeScript where to look for typings for each module.@lit/ts-transformers@1.1.3
Patch Changes
#3116
7d185b4e
- Upgraded TypeScript version to ~4.7.4#3136
afff4c17
- Upgrade ts-clone-node dependency