npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@vaadin-component-factory/vcf-enhanced-crud

v1.6.0

Published

vcf-enhanced-crud

Downloads

40

Readme

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

Published on Vaadin  Directory Stars on vaadin.com/directory

<vaadin-crud>

Live Demo ↗ | API documentation ↗

<vaadin-crud> is a Web Component for CRUD operations. It is part of the Vaadin components.

<vaadin-crud items='[{"name": "Juan", "surname": "Garcia"}]'>
</vaadin-crud>

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-crud:

bower i vaadin/vaadin-crud --save

Once installed, import it in your application:

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

Polymer 3 and ES Modules compatible version

Install vaadin-crud:

npm i @vaadin/vaadin-crud --save

Once installed, import it in your application:

import '@vaadin/vaadin-crud/vaadin-crud.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-crud.html

  • The component with the Material theme:

    theme/material/vaadin-crud.html

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

    vaadin-crud.html

Running demos and tests in browser

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

  2. Make sure you have npm installed.

  3. When in the vaadin-crud 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 npm start, 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/vaadin-crud/demo
  • http://127.0.0.1:8080/components/vaadin-crud/test

Running tests from the command line

  1. When in the vaadin-crud 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

Commercial Vaadin Add-on License version 3 (CVALv3). For license terms, see LICENSE.

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