c706d845eb
* feat: restart config on add, remove, update * fix: reload for root project configs only * fix: throw when userConfigPath can't resolve * chore: changeset * wip: remove normalizePath before writeFile * refactor: invalidateWithCache -> isConfigReload * wip: mustExist? * debug: config loaded successfully * debug: more logs * debug: MORE logging * fix: normalize resolved config path * debug: yet MORE logging * chore: bump proload * fix: use file path, not URL.pathname * Revert "wip: mustExist?" This reverts commit 8ca8662132532dcdc9fd120868e615ddc60f498e. * chore: remove console log * feat: cleanup restart message, better invalid config handling * chore: update lockfile * chore: fix types * fix: throw helpful error when config does not exist * docs: remove "restart dev server" from integrations * docs: make sure to restart -> try restarting Co-authored-by: Nate Moore <nate@astro.build>
119 lines
4.1 KiB
Markdown
119 lines
4.1 KiB
Markdown
# @astrojs/lit 🔥
|
|
|
|
This **[Astro integration][astro-integration]** enables server-side rendering and client-side hydration for your [Lit](https://lit.dev/) custom elements.
|
|
|
|
## Installation
|
|
|
|
There are two ways to add integrations to your project. Let's try the most convenient option first!
|
|
|
|
### `astro add` command
|
|
|
|
Astro includes a CLI tool for adding first party integrations: `astro add`. This command will:
|
|
1. (Optionally) Install all necessary dependencies and peer dependencies
|
|
2. (Also optionally) Update your `astro.config.*` file to apply this integration
|
|
|
|
To install `@astrojs/lit`, run the following from your project directory and follow the prompts:
|
|
|
|
```sh
|
|
# Using NPM
|
|
npx astro add lit
|
|
# Using Yarn
|
|
yarn astro add lit
|
|
# Using PNPM
|
|
pnpm astro add lit
|
|
```
|
|
|
|
If you run into any issues, [feel free to report them to us on GitHub](https://github.com/withastro/astro/issues) and try the manual installation steps below.
|
|
|
|
### Install dependencies manually
|
|
|
|
First, install the `@astrojs/lit` integration like so:
|
|
|
|
```sh
|
|
npm install @astrojs/lit
|
|
```
|
|
|
|
Most package managers will install associated peer dependencies as well. Still, if you see a "Cannot find package 'lit'" (or similar) warning when you start up Astro, you'll need to install `lit` and `@webcomponents/template-shadowroot`:
|
|
|
|
```sh
|
|
npm install lit @webcomponents/template-shadowroot
|
|
```
|
|
|
|
Now, apply this integration to your `astro.config.*` file using the `integrations` property:
|
|
|
|
__`astro.config.mjs`__
|
|
|
|
```js
|
|
import lit from '@astrojs/lit';
|
|
|
|
export default {
|
|
// ...
|
|
integrations: [lit()],
|
|
}
|
|
```
|
|
|
|
## Getting started
|
|
|
|
To use your first Lit component in Astro, head to our [UI framework documentation][astro-ui-frameworks]. This explains:
|
|
- 📦 how framework components are loaded,
|
|
- 💧 client-side hydration options, and
|
|
- 🪆 opportunities to mix and nest frameworks together
|
|
|
|
However, there's a key difference with Lit _custom elements_ over conventional _components_: you can use the element tag name directly.
|
|
|
|
Astro needs to know which tag is associated with which component script. We expose this through exporting a `tagName` variable from the component script. It looks like this:
|
|
|
|
__`src/components/my-element.js`__
|
|
|
|
```js
|
|
import { LitElement, html } from 'lit';
|
|
|
|
const tagName = 'my-element';
|
|
|
|
export class MyElement extends LitElement {
|
|
render() {
|
|
return html` <p>Hello world! From my-element</p> `;
|
|
}
|
|
}
|
|
|
|
customElements.define(tagName, MyElement);
|
|
```
|
|
|
|
> Note that exporting the `tagName` is __required__ if you want to use the tag name in your templates. Otherwise you can export and use the constructor, like with non custom element frameworks.
|
|
|
|
In your Astro template import this component as a side-effect and use the element.
|
|
|
|
__`src/pages/index.astro`__
|
|
|
|
```astro
|
|
---
|
|
import {MyElement} from '../components/my-element.js';
|
|
---
|
|
|
|
<MyElement />
|
|
```
|
|
|
|
> Note that Lit requires browser globals such as `HTMLElement` and `customElements` to be present. For this reason the Lit renderer shims the server with these globals so Lit can run. You *might* run into libraries that work incorrectly because of this.
|
|
|
|
### Polyfills & Hydration
|
|
|
|
The renderer automatically handles adding appropriate polyfills for support in browsers that don't have Declarative Shadow DOM. The polyfill is about *1.5kB*. If the browser does support Declarative Shadow DOM then less than 250 bytes are loaded (to feature detect support).
|
|
|
|
Hydration is also handled automatically. You can use the same hydration directives such as `client:load`, `client:idle` and `client:visible` as you can with other libraries that Astro supports.
|
|
|
|
```astro
|
|
---
|
|
import {MyElement} from '../components/my-element.js';
|
|
---
|
|
|
|
<MyElement client:visible />
|
|
```
|
|
|
|
The above will only load the element's JavaScript when the user has scrolled it into view. Since it is server rendered they will not see any jank; it will load and hydrate transparently.
|
|
|
|
### More documentation
|
|
|
|
Check our [Astro Integration Documentation][astro-integration] for more on integrations.
|
|
|
|
[astro-integration]: https://docs.astro.build/en/guides/integrations-guide/
|
|
[astro-ui-frameworks]: https://docs.astro.build/en/core-concepts/framework-components/#using-framework-components
|