|
1 | | - |
2 | | -[](https://www.webcomponents.org/element/vaadin/vaadin-list-mixin) |
3 | | -[](https://travis-ci.org/vaadin/vaadin-list-mixin) |
4 | | -[](https://gitter.im/vaadin/web-components?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge) |
5 | | - |
6 | 1 | # vaadin-list-mixin |
| 2 | + |
7 | 3 | `vaadin-list-mixin` is a mixin for `nav` elements, facilitating navigation and selection of childNodes. |
8 | 4 |
|
| 5 | +[](https://www.npmjs.com/package/@vaadin/vaadin-list-mixin) |
| 6 | +[](https://discord.gg/PHmkCKC) |
| 7 | + |
9 | 8 | ## Running tests in browser |
10 | 9 |
|
11 | 10 | 1. Fork the `vaadin-list-mixin` repository and clone it locally. |
12 | 11 |
|
13 | | -1. Make sure you have [npm](https://www.npmjs.com/) and [Bower](https://bower.io) installed. |
14 | | - |
15 | | -1. When in the `vaadin-list-mixin` directory, run `npm install` and then `bower install` to install dependencies. |
16 | | - |
17 | | -1. Make sure you have [polymer-cli](https://www.npmjs.com/package/polymer-cli) installed globally: `npm i -g polymer-cli`. |
18 | | - |
19 | | -1. Run `npm start`. |
| 12 | +1. Make sure you have [npm](https://www.npmjs.com/). |
20 | 13 |
|
21 | | -1. Navigate to http://127.0.0.1:3000/components/vaadin-list-mixin/test/index.html |
| 14 | +1. When in the `vaadin-list-mixin` directory, run `npm install` to install dependencies. |
22 | 15 |
|
| 16 | +1. Run `npm test` to start the tests in Chrome. |
23 | 17 |
|
24 | | -## Running tests from the command line |
25 | 18 |
|
26 | | -1. Install [web-component-tester](https://www.npmjs.com/package/web-component-tester): `npm install -g web-component-tester` |
| 19 | +## Debugging tests in browser |
27 | 20 |
|
28 | | -1. When in the `vaadin-list-mixin` directory, run `wct` or `npm test` |
| 21 | +1. Run `npm run debug`, then choose manual mode (M) and open the link in browser. |
29 | 22 |
|
30 | 23 |
|
31 | 24 | ## Following the coding style |
32 | 25 |
|
33 | | -We are using [ESLint](http://eslint.org/) 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. |
| 26 | +We are using [ESLint](http://eslint.org/) 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. |
34 | 27 |
|
35 | 28 |
|
36 | 29 | ## Contributing |
|
0 commit comments