viselect and the README that is only a signpost
✨ Viselect - A high performance and lightweight library to add a visual way of selecting elements, just like on your Desktop. Zero dependencies, super small. Support for major frameworks!
At a glance
- What is it?
- A dependency-free library for desktop-style element selection on the web, with first-party packages for React, Preact and Vue. Its README is 144 words long and contains no install command and no code, its pipeline fixes lint errors instead of failing on them, and its only runtime requirement lives in a manifest marked private.
- Who is it for?
- viselect fits someone adding a selection overlay to an existing interface, who wants the behaviour of a desktop file manager without adopting a component framework's own selection model. Four things to know before you start.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 63 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- simonwep/viselect2,958 ★ · +4
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| simonwep/viselect | 3k | 3k |
4 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
A 144-word README with no install command and no code
The whole file is short enough to describe in one breath: an empty heading block where a logo would be, one line calling it a visual DOM-selection library, a row of three links to documentation, a quickstart and an examples page, a features list of six bullets, a getting-started sentence that tells you to head over to the documentation, and a contributing link. There is no install command, no import statement, no configuration object and no example. So the repository is a signpost rather than a manual, and no install line should be invented for it: what can be said from these files is only where the instructions live. For a library whose selling point is that it is small and has no dependencies, the absence of a two-line quick start in the README is a strange place to be frugal.
Three of the six header blocks are empty containers
The document is written in HTML rather than Markdown, and the consequence is visible in the copy. It opens with a centred heading element that contains nothing, then the tagline, then the centred link row. After that come two centred paragraph blocks that are also empty, and those are where the sponsor badge and the test workflow badge would sit. The links that do survive are the sponsor profile and the test workflow. So a reader of this file sees a header with holes in it, and the repository's own presentation layer is the first thing the text has to explain around. Small, but it is the sort of detail that shows a file assembled from a template and then edited by hand.
The CI script fixes your lint problems instead of failing on them
The workspace root has a separate script for continuous integration, and its first step is the fix variant of the lint task, not the check variant. After that it builds the packages, builds the documentation site, and runs the tests. So a pipeline run does not reject a file for style; it rewrites the file and carries on, which is convenient on a laptop and surprising in a review, because the diff you get back may include formatting you did not write. The second observation is that the documentation build is part of the same gate. A library change that breaks a documentation page fails the run, which is a defensible choice for a project whose README is a signpost and whose documentation is the product.
Releasing is three thin wrappers around a version command
There are three release scripts and none of them does anything except call the workspace version command recursively, once for a patch, once for a minor and once for a major. There is no changelog generator, no version bump script and no publish command anywhere in the root manifest. That is consistent with the root being marked private: it is a container for the workspace rather than a package, so whatever reaches a registry is decided inside the individual packages. The practical consequence for a contributor is that cutting a release is a two-step conversation with whoever owns the packages, and that the root's three friendly script names promise more automation than they deliver.
Node 24 is required by a manifest nobody installs
The root manifest names a package manager and pins a Node major version, and it is the only place in the repository where a runtime requirement appears. The README does not mention Node, and the packages the workspace builds are for browsers, where the version of Node used to build them is not part of the contract. So the constraint is real for anyone cloning the repository, it is invisible to anyone reading the documentation, and it lives in a file explicitly marked private. It is the sort of detail a contributor discovers by running the build on the wrong machine, which is a slower way to learn it than a line in the README would be.
Dependency-free core, three first-party adapters
The first feature bullet sets out the shape of the package: a dependency-free core, plus first-party packages for React, Preact and Vue 3. That is a workspace with one library and three thin adapters, and the tree matches it, holding a packages directory, a documentation directory, a flat lint configuration, a workspace definition file and a workspace lock file, and nothing else of substance. It also puts the zero-dependency claim in context. The claim is about the core, and the adapters are where framework coupling lives, so a project on a framework without an adapter is the case the README does not address, and the documentation is where you would find out whether one exists.
Every stage of a selection is observable and cancellable
The remaining bullets describe the interaction model, and they are unusually concrete about it. Natural interactions means drag, click or tap, and Shift range selection. Configurable behaviour names four specific knobs: selection triggers, thresholds, intersections and overlap handling. Touch and scroll awareness covers touch input and containers scrollable on two axes. Lifecycle events can be observed or cancelled at every stage of a selection. And a programmatic API covers managing selections, refreshing the set of selectable elements, and turning selection off entirely. That last one is the feature worth checking first, because an overlay you can disable is much easier to adopt incrementally than one you have to remove.
Editorial conclusion
viselect fits someone adding a selection overlay to an existing interface, who wants the behaviour of a desktop file manager without adopting a component framework's own selection model. Four things to know before you start. Everything you need to type lives in the documentation site, because this repository's README contains no install command and no sample, so budget a trip there rather than expecting to read the repository and begin. The interactions are configurable at every stage, including thresholds, overlap handling and the ability to cancel mid-selection, which is where the real design questions live. The core carries no dependencies and the framework coupling sits in the three first-party adapters, so pick the one matching your framework and ignore the rest. And if you plan to contribute, note that the pipeline reformats your code rather than rejecting it, which is convenient locally and surprising in review.
Frequently asked questions
What is Viselect?
A library for adding a visual, desktop-style way of selecting elements on a web page. Its core has no dependencies, and it ships first-party packages for React, Preact and Vue 3, supporting drag, click or tap, and Shift range selection.
How do I get started with Viselect?
The README carries no install command and no code sample. It links to the documentation site, with separate quickstart and examples pages, and its getting-started line sends you there.
Which frameworks does Viselect support?
React, Preact and Vue 3, through first-party packages published from the same workspace as the dependency-free core.
Can Viselect selection be configured or cancelled?
Yes. The feature list names selection triggers, thresholds, intersections and overlap handling as configurable, lifecycle events that can be observed or cancelled at every stage of a selection, and a programmatic API for managing selections, refreshing selectable elements, and enabling or disabling selection.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/simonwep-viselect)Star history chart for your README
[](https://hysenlabs.com/projects/simonwep-viselect)Was this useful?