Website profiles · Technology insights · Alternatives

vanillalist.top

Find the best JavaScript plugins, components & libraries for your next project in this handpicked collection of lightweight tools and save time as a developer!

No paid content found
Visit website
Profile views 15 Outbound visits 17 Normal
Vanilla List • The Vanilla JavaScript Repository Full homepage screenshot

At a glance

Category
Development
Language
English
Paid-content signal
No paid content foundObserved
Registered
2017
Hosting
NetlifyInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is Vanilla List?

Vanilla List is a handpicked directory of small, dependency-free JavaScript plugins and components — tools written in plain ("vanilla") JavaScript rather than tied to a framework like React, Vue or jQuery. The idea is to help developers find lightweight building blocks they can drop into any project without pulling in a large framework or a chain of dependencies.

What you'll find there

The collection leans toward focused, single-purpose UI and interaction utilities. Examples from the page include:

  • Menus and navigation — a responsive mega menu and a plugin for the "priority+" navigation pattern, where items that don't fit collapse into a scrollable or controlled area.
  • Sliders, tabs and modals — a carousel-slider, a tabs slider, a modal dialog plugin, and a small toggle for building collapse/accordion/tab/dropdown behaviour.
  • Inputs and forms — a multiselect, an accessible date picker, a colour picker, and a file-upload library.
  • Media and visual effects — a responsive video poster, an image editor, animated gradients, a parallax engine, and animation libraries.

Most entries link out to a live demo, a GitHub repository and often an npm package, so you can inspect the source and try it before committing.

Who it's for

It suits developers who want to keep page weight and dependency count low, or who are working in environments where a full framework is overkill — static sites, server-rendered pages, embedded widgets, or legacy codebases. It's less useful if you're already deep in a framework ecosystem and prefer components designed for it.

Trade-offs to weigh

Because entries are independent projects, quality, maintenance activity and browser support vary from one to the next. A directory listing isn't a guarantee of ongoing upkeep, so check the repository's recent commits, open issues and licence before adopting anything for production. "No dependencies" also doesn't automatically mean small or accessible — verify bundle size and test with a keyboard and screen reader yourself.

Next step

Start from the category closest to your task — say, a date picker or a modal — open two or three candidates, and compare their demos, repository activity and licence side by side. If you want a broader frame of reference, established general-purpose options include MDN Web Docs for understanding the underlying browser APIs, and GitHub for judging a project's health.

How do I choose the right vanilla JavaScript library for a specific feature like a slider or modal?

Start by defining the feature's job, then filter the list by dependency weight, accessibility, and how easily you can replace the library later. Vanilla List is a handpicked repository of dependency-free or lightweight JavaScript plugins and components, and its entries usually link to a demo, GitHub source, and npm package, so you can inspect behavior before committing.

A practical selection workflow

  1. Write one sentence describing the feature and its constraints, for example: "A touch-friendly slider for a marketing page, no build step, must work without jQuery."
  2. Shortlist two or three candidates with live demos.
  3. Test each in a small page with your real content: long text, slow images, keyboard-only navigation, and a narrow mobile viewport.
  4. Check the repository activity and whether the API is small enough to learn in an afternoon.
  5. Decide whether you could write a minimal version yourself. If yes, the library must save meaningful time or add real robustness.

What to compare

Criterion Why it matters What to look for
Dependencies Extra libraries increase bundle size and upgrade risk A vanilla or zero-dependency build
Accessibility Sliders, modals, and dropdowns often break keyboard and screen-reader use Focus management, ARIA attributes, escape-key handling
Customization You will need to match an existing design CSS variables, class hooks, or clear options
Maintenance Unmaintained code becomes a security and compatibility problem Recent commits, issues answered, clear versioning
Integration Your stack may be plain HTML, a CMS, or a framework Whether it works without a bundler or framework wrapper

For a slider, Vanilla List includes options such as swiffyslider.js, described as a light and full-featured slider, and Tabs slider, a pure-JavaScript tabs slider. For modal dialogs, Glory modal is listed as a pure-JavaScript modal dialog plugin. For broader UI state changes, Tiny UI Toggle handles collapse, accordion, tabs, dropdown, and modal patterns. These are concrete starting points, but the right choice depends on your exact interaction: a simple image carousel has different needs from a multi-step form or a navigation mega menu.

Example decision

Suppose you need a modal for a newsletter signup on a static site. A pure-JavaScript modal plugin may be enough if it traps focus and closes on Escape. If your modal must also work as a dropdown or accordion elsewhere, a state-toggle utility could reduce the number of separate dependencies. If accessibility is a hard requirement, test with a keyboard and a screen reader before adopting either.

A useful next step is to open two or three demos from Vanilla List side by side, then build the same small feature with each. The one that survives your real content and keyboard testing is usually the better fit.

Can I use these JavaScript plugins in frameworks like React or Vue?

Yes. The plugins on Vanilla List are plain JavaScript, so they can be used inside React, Vue, Svelte, or any other framework. The catch is that you usually need a thin wrapper to connect the plugin's imperative API to the framework's component lifecycle.

How the integration usually works

Vanilla plugins typically expose a constructor or an init function that takes a DOM element. Frameworks give you a reference to that element and a place to run setup and teardown.

  • React: get a DOM node with useRef, call the plugin inside useEffect, and destroy it in the cleanup function.
  • Vue: use a template ref, call the plugin in onMounted, and clean up in onUnmounted.
  • Svelte: bind the element, run the plugin in onMount, and return a cleanup function.

The pattern is the same everywhere: create the plugin after the element exists, and destroy it before the element is removed.

What to check before choosing a plugin

Question Why it matters
Does it expose a destroy() or dispose() method? Without one, you leak listeners and observers on every re-render.
Does it let you update options after init? Frameworks re-render often; a plugin that only reads options once will fight your state.
Does it manipulate the DOM it was given? If it moves or replaces nodes, React and Vue can get confused about what they own.
Is it framework-agnostic by design? Libraries like Tom Select, FilePond, and Duet Date Picker are commonly wrapped for React and Vue, which suggests the API is predictable.

A concrete scenario

You want a custom multiselect in a React form. You pick a vanilla select library, render an empty <select> through a ref, initialize the plugin in useEffect, and pass the selected values back up through a callback. When the component unmounts, you call destroy(). The form state stays in React; the plugin only handles the visual control.

If you would rather not write wrappers, look for plugins that already publish official React or Vue packages — several of the tools listed, such as FilePond and Tom Select, have community or first-party bindings.

Practical rule

Use a vanilla plugin directly when it is mostly presentational and self-contained. Write a wrapper when the plugin holds state you need to sync, or when it renders lists and options that your framework also wants to control.

How do I install and integrate a plugin from Vanilla List into my project?

Vanilla List is a directory, not a package manager, so installation always happens at the source project rather than on the site itself. Each listing links out to a demo, a GitHub repository and, where available, an npm package. Your job is to pick the right delivery method from those links and wire it into your build.

Choose your install path

Listing shows Typical install Best when
npm link npm install <package-name> You use a bundler (Vite, webpack, esbuild) and want versioning and updates
GitHub only Download the repo or copy the source file into your project The plugin is a single small file, or has no published package
Demo only Read the demo page source to see how it is initialised You need to confirm the API before committing to it

A concrete integration example

Suppose you pick a slider-style plugin such as swiffyslider.js. The pattern is nearly identical across the directory's listings:

  1. Install or copy the file, then import it: import SwiffySlider from 'swiffyslider'.
  2. Add the markup the plugin expects, usually a container with child slides.
  3. Initialise it after the DOM is ready, passing options for autoplay, loop or breakpoints.
  4. Import the plugin's CSS if it ships one, otherwise style the generated classes yourself.
  5. Destroy or re-initialise on route changes if you use a client-side router.

For a dependency-free plugin like Coloris or LetMeScroll.js, you can also drop the file in via a <script> tag and use the global it exposes, which suits static pages with no build step.

Practical checks before you commit

  • Confirm the plugin is framework-agnostic; "vanilla" means no jQuery or framework dependency, not that it works with every stack.
  • Check the last commit date on the linked repository, since a directory can list tools that are no longer maintained.
  • Test the demo on a small screen and with keyboard navigation before adopting it.
  • Prefer npm installs when available so you can update and audit versions.

If you want alternatives in the same category, browse the repository directly at Vanilla List and compare the demo, GitHub and npm links side by side.

Are the plugins on Vanilla List free and open-source?

Most entries on Vanilla List are free to use and lean toward open-source, but the listing itself doesn't guarantee a single license across the board. The repository is a handpicked directory of lightweight JavaScript plugins, components and libraries, and each entry links out to its own demo, GitHub repository and npm page. Those external links—not the directory page—are where the actual license lives.

What the page shows

  • Each plugin card includes links such as demo, github and npm.
  • The collection focuses on "lightweight tools" written in vanilla JavaScript, with examples like snazzymenu.js, swiffyslider.js, Tom Select, lax.js, granim.js, Duet Date Picker, Coloris, FilePond and anime.js.
  • The page presents these as practical building blocks, not as a paid product catalog.

Why "free" and "open-source" aren't automatic

A GitHub repository can be public without an open-source license, and an npm package can be free to install while carrying restrictive terms. Some projects also use dual licensing: a free open-source version plus a paid commercial tier or add-on. The directory doesn't appear to state a uniform license, so the safe assumption is per-project.

How to check before you commit

  1. Open the plugin's github link and look for a LICENSE file at the repository root.
  2. Confirm the license type: MIT and Apache-2.0 are permissive; GPL can affect how you distribute your own code.
  3. Check the npm page for the license field and any notes about commercial use.
  4. If the project offers a paid tier, verify that the free version covers your use case.

For a concrete example: if you're building a commercial dashboard and want to use a color picker, start with Vanilla List to find candidates, then check the license on the linked repository before shipping. For broader comparisons, GitHub and npm show the license metadata directly.

How can I contribute a plugin to Vanilla List?

Vanilla List doesn't publish a contribution process on its own pages, so the short answer is that you can't submit a plugin through a documented path on the site itself. The directory presents each entry as a card with demo, GitHub and npm links, and the collection reads as handpicked rather than open-submission. That means the practical route is to reach the maintainers through the project's public channels rather than a form.

What to do instead

  • Check the site footer or an "About" page for a contact address or repository link — that's where submission guidelines usually live when a directory has no visible submit button.
  • Look for the project on GitHub. If the repository is public, open an issue titled something like "Plugin suggestion: [name]" and include the demo URL, the repo URL and a short description of what the plugin does and its dependencies.
  • If no contact route is visible, treat the listing as editorially curated and expect no guaranteed response.

What a strong submission looks like

The entries on the page share a clear pattern, so match it:

Detail Why it matters here
Working demo Every listed item has one; it's the fastest way for a reviewer to judge it
Public repo All entries link to GitHub
npm package Most entries include an npm link
No dependencies The directory is framed around vanilla JavaScript
Small footprint "Lightweight" is the recurring selling point in the descriptions

A concrete scenario

Suppose you've written a dependency-free tooltip plugin. Before pitching it, confirm it works without jQuery or a framework, publish it to npm, put a live demo on a static host, and write a README that states the file size and browser support. Then send one short message containing those four links. A reviewer scanning a queue of suggestions can evaluate that in under a minute; a plugin with no demo or an unclear dependency chain usually gets skipped.

Decision criterion

If you need guaranteed inclusion or a defined review timeline, a curated directory is the wrong target — publish on npm and promote it through communities like Reddit's r/javascript or Hacker News instead. Treat a Vanilla List listing as an editorial nod you earn, not a submission you complete.

Related questions

More questions →
What is vanillalist.top?
Find the best JavaScript plugins, components & libraries for your next project in this handpicked collection of lightweight tools and save time as a developer!
Does vanillalist.top offer paid content?
Unknown.
What languages does vanillalist.top support?
Primary language: English.
How can I visit vanillalist.top?
Use the Visit website link to open the website in a new tab.
What are some alternatives to vanillalist.top?
Related websites include zzzcode.ai, zyte.com, zustand.docs.pmnd.rs, zustand-demo.pmnd.rs, zulko.github.io, zmk.dev. Compare their features and pricing for your needs.

Website Overview

Identifiable technologies and additional version or configuration signals make the service easier to fingerprint, which may help targeted scanners narrow their checks. An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality.

Domain and Registration

Registered in 2017, this domain has about 9 years of history. That suggests continuity, although ownership and purpose may have changed. Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The registrar is Gandi SAS, a widely used domain service provider. Registration contact information is publicly available through RDAP. The domain uses the common .top extension, which is not an independent safety signal.

DNS and Email

The observed email authentication setup is incomplete: DMARC is missing. Nameservers are provided by gandi.net, indicating managed DNS hosting. MX records point to the gandi.net email service. No CNAME was found; the observed records resolve directly to addresses. DNSSEC signatures were not detected, so this additional DNS authenticity protection is not confirmed.

TLS and Certificates

The public key uses EC with 256 bits. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued by Let's Encrypt, commonly associated with automated certificate services. The certificate's total validity is about 89 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: Permissions-Policy. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. No obvious internal addresses or debug information were found in the headers. The Server header contains the custom value Netlify. No explicit CDN or WAF marker was found in the response headers.

Technology Stack Analysis

The public page identifies Eleventy 3.1.2, Netlify, with exact versions exposed for 1 technologies. These details can narrow vulnerability checks, although exposure alone is not a vulnerability.

Search and Social Sharing

The Generator tag identifies Eleventy v3.1.2, making the publishing system easier to fingerprint. Twitter Card metadata is configured. The title has 48 characters, within a common display range. A meta description is present, with 159 characters. The observed directives allow indexing and link following.

Hosting and Email

DNSgandi.net
HostingNetlify
Emailgandi.net
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) United States flagUnited States Inferred 75.2.60.5

Registration details

RDAP / WHOIS

RegistrarGandi SAS
Registered2017-08-07
Expires2027-08-07
Domain statusclient transfer prohibited
Nameserversns-149-c.gandi.net、ns-207-b.gandi.net、ns-61-a.gandi.net
DNSSECunsigned

DNS records

DNS

TypeNameValueTTLPriority
Avanillalist.top75.2.60.5800—
MXvanillalist.topspool.mail.gandi.net80010
MXvanillalist.topfb.mail.gandi.net80050
NSvanillalist.topns-149-c.gandi.net10800—
NSvanillalist.topns-207-b.gandi.net10800—
NSvanillalist.topns-61-a.gandi.net10800—
TXTvanillalist.topahrefs-site-verification_c7b6081d5f66eb03c82dac996c3849e60036574503b66da960fc8e4a0d1e0f0d500—
TXTvanillalist.topv=spf1 include:_mailcust.gandi.net ?all500—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectvanillalist.top
IssuerLet's Encrypt
Valid until2026-11-10T14:03 · Remaining when checked: 39 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=UTF-8
cache-controlpublic,max-age=0,must-revalidate
serverNetlify
strict-transport-securitymax-age=31536000
content-security-policydefault-src 'none'; style-src 'self'; form-action 'self'; script-src 'self' a-little-feedback.guerilla.studio; connect-src 'self' a-little-feedback.guerilla.studio; img-src 'self'; base-uri 'self';
x-frame-optionsDENY
x-content-type-optionsnosniff
referrer-policyno-referrer-when-downgrade

Identified technologies

Eleventy 3.1.2Netlify

Pages, Search and Sharing

Meta descriptionFind the best JavaScript plugins, components & libraries for your next project in this handpicked collection of lightweight tools and save time as a developer!
Canonical URLhttps://vanillalist.top/
LanguageEnglish (default)
Twitter Cardsummary_large_image
All bots 1 allowed · 0 disallowed
  • Allow/
adsbot-google 0 allowed · 1 disallowed
  • Disallow/
amazonbot 0 allowed · 1 disallowed
  • Disallow/
applebot 0 allowed · 1 disallowed
  • Disallow/
applebot-extended 0 allowed · 1 disallowed
  • Disallow/
anthropic-ai 0 allowed · 1 disallowed
  • Disallow/
awariorssbot 0 allowed · 1 disallowed
  • Disallow/
awariosmartbot 0 allowed · 1 disallowed
  • Disallow/
bytespider 0 allowed · 1 disallowed
  • Disallow/
ccbot 0 allowed · 1 disallowed
  • Disallow/
chatgpt 0 allowed · 1 disallowed
  • Disallow/
chatgpt-user 0 allowed · 1 disallowed
  • Disallow/
claudebot 0 allowed · 1 disallowed
  • Disallow/
claude-web 0 allowed · 1 disallowed
  • Disallow/
cohere-ai 0 allowed · 1 disallowed
  • Disallow/
dataforseobot 0 allowed · 1 disallowed
  • Disallow/
diffbot 0 allowed · 1 disallowed
  • Disallow/
facebookbot 0 allowed · 1 disallowed
  • Disallow/
google-extended 0 allowed · 1 disallowed
  • Disallow/
gptbot 0 allowed · 1 disallowed
  • Disallow/
imagesiftbot 0 allowed · 1 disallowed
  • Disallow/
magpie-crawler 0 allowed · 1 disallowed
  • Disallow/
omgili 0 allowed · 1 disallowed
  • Disallow/
omgilibot 0 allowed · 1 disallowed
  • Disallow/
peer39_crawler 0 allowed · 1 disallowed
  • Disallow/
perplexitybot 0 allowed · 1 disallowed
  • Disallow/
youbot 0 allowed · 1 disallowed
  • Disallow/

User reviews (0)

  • No reviews yet.