JSPM

@vaadin/vaadin-button

2.0.0-pre.2
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 11381
  • Score
    100M100P100Q149820F
  • License Apache-2.0

vaadin-button

Package Exports

  • @vaadin/vaadin-button
  • @vaadin/vaadin-button/src/vaadin-button.js
  • @vaadin/vaadin-button/theme/lumo/vaadin-button-styles.js
  • @vaadin/vaadin-button/theme/lumo/vaadin-button.js
  • @vaadin/vaadin-button/vaadin-button
  • @vaadin/vaadin-button/vaadin-button.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@vaadin/vaadin-button) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Bower version npm version Published on webcomponents.org Build Status Gitter

<vaadin-button>

Live Demo ↗ | API documentation ↗

<vaadin-button> is a Polymer 2 element 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

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

License

Apache License 2.0

Vaadin collects development time usage statistics to improve this product. For details and to opt-out, see https://github.com/vaadin/vaadin-usage-statistics.