-
Notifications
You must be signed in to change notification settings - Fork 220
Lit 3.0 pre-releases blog post #1115
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
66 changes: 66 additions & 0 deletions
66
packages/lit-dev-content/site/blog/2023-05-15-lit-3.0-prerelease.md
This file contains hidden or 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,66 @@ | ||
--- | ||
tags: blogPosts | ||
layout: blog-post.html | ||
title: "Announcing Lit 3.0 Pre-releases" | ||
summary: "Get an early look at the upcoming Lit 3.0 release." | ||
date: 2023-05-15 | ||
author: | ||
- justin-fagnani | ||
--- | ||
|
||
# Announcing Lit 3.0 Pre-releases | ||
|
||
The Lit team is excited to announce the first pre-releases of Lit 3.0! | ||
|
||
Lit 3.0 is our first major version since [introducing the unified Lit project and Lit 2.0](https://lit.dev/blog/2021-04-21-lit-2.0-meet-lit-all-over-again/) two years ago. We really value stability and backwards compatibility for our community, so we've focused on adding new features with minor versions of the core libraries and new labs packages, and not making any breaking changes. | ||
|
||
But the time is right for just a few breaking changes that will improve development velocity and testing stability on the core Lit project. | ||
|
||
## Changes | ||
|
||
Lit 3.0 adds no new features, because new features are generally not breaking changes and can be added in minor versions, according to semver. The Lit 3.0 release is an opportunity to make a few breaking changes that trim out some technical debt to unlock new features we have scheduled for our 3.x release series. | ||
|
||
The Lit 3.0 changes are mostly in browser support, removing deprecated APIs, and how packages are published. If you run Lit 2.x with no deprecation warnings, this should be a seamless upgrade! | ||
|
||
Here are the biggest things Lit 3.0 changes: | ||
- IE11 is no longer supported. | ||
- Lit's npm modules are now published as ES2021. | ||
- APIs deprecated during the Lit 1.x release timeframe have been removed. | ||
- SSR hydration support modules were moved to the `@lit-labs/ssr-client` package. | ||
|
||
A preview of the [Lit v2 to v3 upgrade guide](/docs/v3/releases/upgrade/) is available on the site. | ||
|
||
Detailed change logs can be found [on GitHub](https://github.com/lit/lit/releases?q=%22-pre.0%22&expanded=true). | ||
|
||
## Trying the Pre-releases | ||
|
||
We would love your help testing the new versions, to ensure a smooth upgrade process with the final releases. We're especially interested in making sure the new language version works with your toolchains. We expect some users may need to upgrade their tooling to the latest versions. | ||
|
||
You can try the pre-releases out by updating your package.json file to include the following: | ||
|
||
```json | ||
"lit": "^3.0.0-pre.0" | ||
"lit-html": "^3.0.0-pre.0" | ||
"lit-element": "^4.0.0-pre.0" | ||
"@lit/reactive-element": "^2.0.0-pre.0" | ||
``` | ||
|
||
You can also use the `pre` npm tag, like `npm i lit@pre`. | ||
|
||
All other packages, like labs packages, have pre-release versions too that depend on the pre-release core libraries. If you depend on those you'll have to update them too. If you're more daring you can use npm overrides to select the pre-releases even for dependencies. This should work for most dependencies. | ||
|
||
Even if dependencies are using Lit 2.x, the good news is that Lit 2.x and Lit 3.x are interoperable, because: | ||
1. The inherent interoperability web components: components built with different libraries work together, including those build with different versions of Lit. | ||
2. We made interop of core features like templates and directives a priority for Lit 2. You can share templates, directives, decorators, etc., across Lit versions. | ||
|
||
## Docs | ||
|
||
We are preparing new docs for 3.0 on [lit.dev](https://lit.dev). Even though these will be mostly the same as 2.x, we are clarifying the browser and toolchain support, and want to make it easy to select the right docs set for the version you're using to enable future changes specific to to 3.x. At the 3.0 launch, we’ll archive the 2.x docs (but they will remain available in the doc version dropdown, as will 1.x). During the 3.0 pre-release phase, 2.x will remain the default, and you select 3.0 from the dropdown next to the Documentation tab. | ||
|
||
## Feedback | ||
|
||
We hope you enjoy Lit 3.0! If you have questions or feedback, please let us know in [GitHub issues](https://github.com/lit/lit/issues) or on our [Lit and Friends Discord](https://lit.dev/discord/). | ||
|
||
**Thanks!,** | ||
|
||
**-The Lit Team** |
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.
Uh oh!
There was an error while loading. Please reload this page.