<foo-element>

Live Demo ↗ | API documentation ↗

<foo-element> is a Web Component providing <element-functionality>, part of the Vaadin components.

<foo-element>
  ...
</foo-element>

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 foo-element:

bower i vaadin/foo-element --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 foo-element:

npm i @vaadin/foo-element --save

Once installed, import it in your application:

import '@vaadin/foo-element/foo-element.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/component-name.html

• The component with the Material theme:

  theme/material/component-name.html

• Alias for theme/lumo/component-name.html:

  component-name.html

Running demos and tests in browser

1. Fork the foo-element repository and clone it locally.

2. Make sure you have npm installed.

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

4. Make sure you have polymer-cli installed globally: npm i -g polymer-cli.

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

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

• http://127.0.0.1:8080/components/foo-element/demo
• http://127.0.0.1:8080/components/foo-element/test

Running tests from the command line

1. When in the foo-element 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.

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.