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

paper-autocomplete

v3.0.0

Published

Custom Autocomplete, used to select 1 element of an array, or one item from a data source

Downloads

52

Readme

Coverage Status Published on NPM Published on webcomponents.org

Paper Autocomplete

Premise: This repo has been forked from OLD polymer element, writing in polymer 1.
I updated to polymer 3, now this web-component it's compabile only with Polymer 3.0.
I'm so sorry but there aren't fork in my project from the original repo.
This is the source Repo

<paper-autocomplete></paper-autocomplete> used to select one element of an array or from a data source.

See: Documentation, Demo.

Usage

Installation

npm install --save paper-autocomplete

In an html file

<html>
  <head>
    <script type="module" src="paper-autocomplete/paper-autocomplete.js"></script>
  </head>
  <body>
    <paper-autocomplete label="Search Something" source={{array}}></paper-autocomplete>
  </body>
</html>

In a Polymer 3 element

import {PolymerElement, html} from '@polymer/polymer';
import 'paper-autocomplete/paper-autocomplete';

class SampleElement extends PolymerElement {
  static get template() {
    return html`
      <paper-autocomplete label="Search Something" source={{array}}></paper-autocomplete>
    `;
  }
}
customElements.define('sample-element', SampleElement);

For Developers

Demo and Docs

Custome Style, from outside

Find some test on the various demo file.

--paper-autocomplete-main-color: Color for autocomplete details (border & icons).
--paper-input-font-color: Font color only for input value.
--paper-suggestions-color: Font color for item suggestions.
--suggestions-item-min-height: Min heigth for item suggestions.
--paper-autocomplete-min-height: Min heigth for the autocomplete, that wrap also the suggestions.

Testing & Demo

First step clone repo & install dependencies:

git clone https://github.com/EmanueleDessi/paper-autocomplete.git
cd paper-autocomplete
npm install

To run test whit polymer use:

npm run test //Test for all installed browser in your pc
npm run test-safari //Test only for safari browser

If you have the problem with polymer test, try this (I use this method):

  1. open the serve with polymer serve;
npm run serve
  1. run debbuger with vscode or open demo path in your localhost by terminal;
open http://localhost:8081/components/paper-autocomplete/test/paper-autocomplete-test.html
Difference Usage between VScode and not

With VScode you see the result and log in the DEBUG CONSOLE.
Without VScode you must use the Inspect Element of your default Browser.
If will you use VScode, remember, you must config the debbuger in .vscode folder.
(my .vscode folder is ignored by gitignore)

To run demo

npm run serve

TODO