The Lit Starter Kits are project templates for reusable Lit components that can be published for others to use.
To get started working on a component locally, you can use one of these starter projects:
Both projects define a Lit component. They also add a set of optional tools for developing, linting, and testing the component:
- Node.js and npm for managing dependencies. Requires Node.js 10 or greater.
- A local dev server, Web Dev Server.
- Linting with ESLint and lit-analyzer.
- Testing with Web Test Runner.
- A static doc site built with web-component-analyzer and eleventy.
None of these tools is required to work with Lit. They represent one possible set of tools for a good developer experience.
Alternative starting point. As an alternative to the official Lit starter projects, the Open WC project has a project generator for web components using Lit. The Open WC script asks a series of questions and scaffolds out a project for you.
Download the starter projectPermalink to “Download the starter project”
The quickest way to try out a project locally is to download one of the starter projects as a zip file.
Download the starter project from GitHub as a zip file:
Uncompress the zip file.
Try out your projectPermalink to “Try out your project”
To watch files and rebuild when the files are modified, run the following command in a separate shell:
Run the dev server:
Open the project demo page in a browser tab. For example:
Your server may use a different port number. Check the URL in the terminal output for the correct port number.
Edit your componentPermalink to “Edit your component”
Edit your component definition. The file you edit depends on which language you're using:
my-element.jsfile in the project root.
- TypeScript. Edit the
my-element.tsfile in the
A couple of things to look for in the code:
The code defines a class for the component (
MyElement) and registers it with the browser as a custom element named
rendermethod defines a template that will be rendered as a part of the component. In this case, it includes some text, some data bindings, and a button. For more information, see Templates.
The component defines some properties. The component responds to changes in these properties (for example, by re-rendering the template when necessary). For more information, see Properties.
Rename your componentPermalink to “Rename your component”
You'll probably want to change the component name from "my-element" to something more appropriate. This is easiest to do using an IDE or other text editor that lets you do a global search and replace through an entire project.
If you're using the TypeScript version, remove generated files:
Search and replace "my-element" with your new component name in all files in your project (except in the
Search and replace "MyElement" with your new class name in all files in your project (except in the
Rename the source and test files to match the new component name:
If you're using the TypeScript version, rebuild the project:
Test and make sure your component is still working:
Next stepsPermalink to “Next steps”
For details on running tests and using other tools, see the starter project README:
For a guide on publishing your component to
npm, see Publishing.