Usage no npm install needed!

<script type="module">
  import vaadinButton from '';


npm version Published on Build Status Coverage Status Gitter

Published on Vaadin Directory Stars on


Live Demo ↗ | API documentation ↗

<vaadin-button> is a Web Component providing an accessible and customizable button, part of the Vaadin components.

<vaadin-button theme="primary">Primary</vaadin-button>
<vaadin-button theme="secondary">Secondary</vaadin-button>
<vaadin-button theme="tertiary">Tertiary</vaadin-button>

Screenshot of vaadin-button, using the default Lumo theme


The Vaadin components are distributed as Bower and npm packages. Please note that the version range is the same, as the API has not changed. You should not mix Bower and npm versions in the same application, though.

Unlike the official Polymer Elements, the converted Polymer 3 compatible Vaadin components are only published on npm, not pushed to GitHub repositories.

Polymer 2 and HTML Imports compatible version

Install vaadin-button:

bower i vaadin/vaadin-button --save

Once installed, import it in your application:

<link rel="import" href="bower_components/vaadin-button/vaadin-button.html">

Polymer 3 and ES Modules compatible version

Install vaadin-button:

npm i @vaadin/vaadin-button --save

Once installed, import it in your application:

import '@vaadin/vaadin-button/vaadin-button.js';

Getting Started

Vaadin components use the Lumo theme by default.

The file structure for Vaadin components

  • src/vaadin-button.html

    Unstyled component.

  • theme/lumo/vaadin-button.html

    Component with Lumo theme.

  • vaadin-button.html

    Alias for theme/lumo/vaadin-button.html

Running demos and tests in browser

  1. Fork the vaadin-button repository and clone it locally.

  2. Make sure you have npm installed.

  3. When in the vaadin-button directory, run npm install and then bower install to install dependencies.

  4. Run polymer serve --open, browser will automatically open the component API documentation.

  5. You can also open demo or in-browser tests by adding demo or test to the URL, for example:

Running tests from the command line

  1. When in the vaadin-button directory, run polymer test

Following the coding style

We are using ESLint for linting JavaScript code. You can check if your code is following our standards by running gulp lint, which will automatically lint all .js files as well as JavaScript snippets inside .html files.

Creating a pull request

  • Make sure your code is compliant with our code linters: gulp lint
  • Check that tests are passing: polymer test
  • Submit a pull request with detailed title and description
  • Wait for response from one of Vaadin components team members


Apache License 2.0

Vaadin collects development time usage statistics to improve this product. For details and to opt-out, see