Vite Package Setup
Get started with a Vite Package, setup with TypeScript and Lit
Last updated
Get started with a Vite Package, setup with TypeScript and Lit
Last updated
Umbraco recommends building extensions with a setup using TypeScript and a build tool such as Vite. Umbraco uses the library Lit for building web components which we will use throughout this guide.
This guide is based on our general recommendations for working with and building extensions for the Umbraco backoffice.
You can use any framework or library, as you are not limited to the mentioned frameworks.
Vite comes with a set of good presets to get you quickly up and running with libraries and languages. For example: Lit, Svelte, and Vanilla Web Components with both JavaScript and TypeScript.
Before following this guide, read the Setup Your Development Environment article.
Open a terminal and navigate to the project folder where you want to create your new Vite Package.
Run the following command in the folder to create a new Vite Package:
This command will set up your new package and ask you to pick a framework and a compiler.
Enter Client as both the Project Name and Package name when prompted.
Choose Lit and TypeScript as the framework and language.
For this tutorial, it is recommended to use the names given above. However, feel free to choose other names if preferred.
This creates a new folder called Client, sets up our new project, and creates a package.json file, which includes the necessary packages. This is where all your source files live.
Alternatively, you can skip the interactive prompts and use this command:
This will create a Vite Package with Lit and TypeScript in a folder called Client.
Navigate to the Client project folder and install the required packages:
Before proceeding, ensure that you install the version of the Backoffice package compatible with your Umbraco installation. You can find the appropriate version on the @umbraco-cms/backoffice npm page.
Install the Backoffice package using the following command:
To avoid installing Umbraco’s sub-dependencies such as TinyMCE and Monaco Editor, you can add the --legacy-peer-deps flag:
Using this flag will disable Intellisense for external references.
Open the tsconfig.json file.
Add the array types inside compilerOptions, with the entry of @umbraco-cms/backoffice/extension-types:
Create a new file called vite.config.ts in the folder and insert the following code:
The outDir parameter specifies where the compiled files are placed. In this example, they are stored in the App_Plugins/Client folder. If you are working with a different structure, such as a Razor Class Library (RCL) project, update this path to wwwroot.
This alters the Vite default output into a library mode, where the output is a JavaScript file with the same name as the name attribute in package.json. The name is client.js if you followed this tutorial with no changes.
The source code that is compiled lives in the src folder of your package folder and that is where you can see a my-element.ts file. You can confirm that this file is the one specified as our entry on the Vite config file that we recently created.
The build:lib:entry parameter can accept an array which will allow you to export multiple files during the build. You can read more about Vite's build options here.
Build the ts file in the Client folder so we can use it in our package:
If you like to continuously work on the package and have each change built, you can add a watchscript in your package.json with vite build --watch. The example below indicates where in the structure this change should be implemented:
Then in the terminal, you can run npm run watch.
Declare your package to Umbraco via a file called umbraco-package.json. This should be added at the root of your package. In this guide, it is inside the Client/public folder so that Vite automatically copies it over every time it builds.
This example declares a Dashboard as part of your Package, using the Vite example element.
Umbraco needs the name of the element that will render as default when our dashboard loads.
This is specified in the manifest as the elementName.
Another approach would be to define your default element in the TS code. To do this, in the src/my-element.ts add default to your MyElement class in the file like so:
Learn more about the abilities of the manifest file in the Umbraco Package Manifest article.
To be able to test your package, you will need to run your site.
Before you do this, you need to make sure to run npm run build to compile your TypeScript files and copy them to the App_Plugins/Client folder.
If you try to include some of these resources via Visual Studio (VS), then make sure not to include TypeScript files. Otherwise, VS will try to include a few lines on your .csproj file to compile the TypeScript code that exists in your project folder. When you run your website, VS will try to compile these files and fail.
The final result looks like this:
Back in the src/my-element.ts file, you can update the styles property to make any styling changes. You can change the background-color of the button to white so it is more visible:
With this, you have set up your Package and created an Extension for the Backoffice.
In more advanced cases, you can add more elements to your package and create more complex extensions. In that case, you can benefit greatly from creating another project in your solution to hold the files. This way, you can keep your solution clean and organized. We recommend creating a Razor Class Library (RCL) for this purpose. You can read more about this in the Development Flow article.
This Dashboard appears in all sections and does not do much. To extend it to interact with the Umbraco Backoffice, follow the tutorial on Creating Your First Extension.
