@vaadin/vaadin-button

WebJar for @vaadin/vaadin-button

License

License

Categories

Categories

Vaadin User Interface Web Frameworks
GroupId

GroupId

org.webjars.npm
ArtifactId

ArtifactId

vaadin__vaadin-button
Last Version

Last Version

2.2.1
Release Date

Release Date

Type

Type

jar
Description

Description

@vaadin/vaadin-button
WebJar for @vaadin/vaadin-button
Project URL

Project URL

http://webjars.org
Source Code Management

Source Code Management

https://github.com/vaadin/vaadin-button

Download vaadin__vaadin-button

How to add to project

<!-- https://jarcasting.com/artifacts/org.webjars.npm/vaadin__vaadin-button/ -->
<dependency>
    <groupId>org.webjars.npm</groupId>
    <artifactId>vaadin__vaadin-button</artifactId>
    <version>2.2.1</version>
</dependency>
// https://jarcasting.com/artifacts/org.webjars.npm/vaadin__vaadin-button/
implementation 'org.webjars.npm:vaadin__vaadin-button:2.2.1'
// https://jarcasting.com/artifacts/org.webjars.npm/vaadin__vaadin-button/
implementation ("org.webjars.npm:vaadin__vaadin-button:2.2.1")
'org.webjars.npm:vaadin__vaadin-button:jar:2.2.1'
<dependency org="org.webjars.npm" name="vaadin__vaadin-button" rev="2.2.1">
  <artifact name="vaadin__vaadin-button" type="jar" />
</dependency>
@Grapes(
@Grab(group='org.webjars.npm', module='vaadin__vaadin-button', version='2.2.1')
)
libraryDependencies += "org.webjars.npm" % "vaadin__vaadin-button" % "2.2.1"
[org.webjars.npm/vaadin__vaadin-button "2.2.1"]

Dependencies

compile (6)

Group / Artifact Type Version
org.webjars.npm : vaadin__vaadin-themable-mixin jar [1.2.1,2)
org.webjars.npm : vaadin__vaadin-lumo-styles jar [1.3.3,2)
org.webjars.npm : vaadin__vaadin-material-styles jar [1.2.0,2)
org.webjars.npm : vaadin__vaadin-element-mixin jar [2.0.0,3)
org.webjars.npm : polymer__polymer jar [3.0.0,4)
org.webjars.npm : vaadin__vaadin-control-state-mixin jar [2.1.1,3)

Project Modules

There are no modules declared in this project.

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

Published on Vaadin  Directory Stars on vaadin.com/directory

<vaadin-button>

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

Installation

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.

To use the Material theme, import the correspondent file from the theme/material folder.

Entry points

  • The component with the Lumo theme:

    theme/lumo/vaadin-button.html

  • The component with the Material theme:

    theme/material/vaadin-button.html

  • Alias for theme/lumo/vaadin-button.html:

    vaadin-button.html

Running demos and tests in a browser

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

  2. Make sure you have npm and Bower installed.

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

  4. Run npm start, 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 npm run lint, which will automatically lint all .js files as well as JavaScript snippets inside .html files.

Big Thanks

Cross-browser Testing Platform and Open Source <3 Provided by Sauce Labs.

Contributing

To contribute to the component, please read the guideline first.

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.

org.webjars.npm

Vaadin

An open platform for building modern web apps for Java back ends

Versions

Version
2.2.1
2.1.0