The plugin is published as devbridge-autocomplete, and its lint script skips the source directory
Ajax Autocomplete for jQuery allows you to easily create autocomplete/autosuggest boxes for text input fields
At a glance
- What is it?
- This jQuery autocomplete plugin has three names in play: the repository, the npm package and the method it registers. Version 2.0 raised the jQuery floor without changing any option name, four npm overrides alias every jQuery major to version 4, the linter is pointed at the tests and the build script rather than at src, and two options that control dropdown positioning only work together.
- Who is it for?
- The plugin is worth a look if you want an autosuggest box on a text field and already ship jQuery, since it has one runtime dependency, a minified UMD bundle of about 13 KB, an ES module build, bundled TypeScript types and no styling to fight. Three things to check before you upgrade to version 2.0.
- 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 4 days ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 22, 2026, and from our analysis. They are not legal advice.
Star history
- tkirda/jQuery-Autocomplete3,532 ★ · -5
| Repository | 2026-09-24 | 2026-11-22 |
|---|---|---|
| tkirda/jQuery-Autocomplete | 3.5k | 3.5k |
-5 Stars in the last 59 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
One plugin, three names
The repository is jQuery-Autocomplete, the README heads itself Ajax Autocomplete for jQuery, and the package you install is neither of those:
npm install devbridge-autocompleteWhen the UMD bundle loads through a script tag it registers two methods on the global jQuery, an autocomplete method and a devbridgeAutocomplete method, so both call sites work. A file at the repository root is named after the package again, a plugin manifest for the jQuery plugin directory format. So there are four names in circulation for one piece of code, and two of them are the published name rather than the descriptive one. That matters in three practical places: the install command, the import in a bundler, and the plugin manifest you would submit if you were publishing to a directory. The homepage in the repository metadata is also written over plain HTTP.
Version 2.0 changed the floor, not the options
The upgrading section is unusually explicit. Version 2.0 drops support for jQuery 1.x and 2.x and drops IE-era browsers. The plugin API and option names are unchanged, so every existing call site continues to work. What changed is the peer dependency, now jquery at 3.0 or newer, and the build target, now evergreen browsers at ES2020. The advice for anyone who cannot move their jQuery is to stay on the 1.5.x line. That is a rare kind of major bump: a consumer reading a changelog would expect something to break, and here the only break is the runtime you are on. It also means the two release lines have to be maintained in parallel for as long as anyone is on old jQuery.
Four overrides alias every jQuery major to version 4
The manifest contains an overrides block with four entries, one each for jquery1, jquery2, jquery3 and jquery4, and all four resolve to the same target, jQuery 4 or newer. Read as a testing scaffold, that looks like a way of installing several jQuery majors side by side under different names. Read against what the README claims, it does not line up: the documented floor is jQuery 3, the peer dependency says 3.0 or newer, and the development dependencies install jQuery 4. So whichever way the overrides are meant to work, the only jQuery actually present in a checkout is version 4, and the types package is the version 4 one. Anyone relying on the compatibility story should verify it rather than take the overrides as a matrix.
The linter never looks at src
Look at the three quality scripts together. Format runs prettier over the source, the test directory and the build script. Format check runs the same check. Lint runs eslint over the test directory and the build script, and the source directory is absent from its arguments. Type checking does cover the source, since it invokes the compiler with no emit. So the source tree is type checked and formatted but not linted, which is the opposite of the usual arrangement and the kind of gap that lets an unused variable or a stray any through. The build itself is a single node script rather than a bundler configuration file, and esbuild is in the development dependencies to do the work.
appendTo and forceFixPosition have to agree
Two options control where the dropdown sits and how it is positioned, and they only work together. The dropdown is appended to the document body by default, and the container is absolutely positioned by the plugin. If you change the target with appendTo, which accepts a jQuery object, a selector or an element, the target needs a positioned style of its own, absolute or relative. But the positioning code only runs when the dropdown is in the body, and forceFixPosition exists precisely to override that. Set appendTo without forceFixPosition and the dropdown is in the right part of the document with no position calculation at all. The documented default for the class on the container is a fixed string, which is the hook you have to override if you want to style it your own way.
Negative results are cached by prefix
preventBadQueries defaults to true and does something worth understanding before you turn it off. When a query returns nothing, the plugin remembers that, and any later query starting with that string is not sent at all. The example in the table is precise: once a query beginning with Jam comes back empty, Jamai will never fire a request. That saves traffic on a search box where the user keeps typing into a dead end, and it costs you the ability to recover if the backend changes mid-session, which is why it is an option. Two neighbouring options have the same flavour. deferRequestBy defaults to zero milliseconds and exists so that fast typists do not trigger a request per keystroke. ignoreParams suppresses the query string payload entirely, for the case where your serviceUrl callback builds the whole URL itself.
Accent-insensitive matches are found but not highlighted
The documentation walks through accent folding properly, and then admits the seam. The default lookup filter is a case-insensitive substring match, so it will not find Cafe when the suggestion is written with an accent. The fix is to pass your own filter that normalises both sides, using Unicode normalisation and a diacritic mark pattern, and the example does exactly that. But the last line of that section says the default result formatter still highlights only exact case-insensitive matches. So after the fix the suggestion appears in the list, is not highlighted inside itself, and you have a second filter to write if you want the highlight too. The grouping key, the formatter and the select callback all receive the untouched data field, which is the extension point for solving this once.
The built bundle is committed
The repository tree contains a dist directory, and the manifest points main, module and types at files inside it. So the compiled output is versioned alongside the source, which is why the README can state a bundle size of about 13 KB minified for the UMD build and describe the ES module build as published for modern bundlers: both are files you can inspect in the tree rather than artefacts you have to build to check. Two other entries are worth noting. The readme is written in lower case while the repository name capitalises it, which only matters on case-sensitive tooling. And the instance method table ends mid-list after clear and clearCache, two methods whose names differ by three letters and whose difference is that the first also drops the current suggestions while the second leaves them.
Editorial conclusion
The plugin is worth a look if you want an autosuggest box on a text field and already ship jQuery, since it has one runtime dependency, a minified UMD bundle of about 13 KB, an ES module build, bundled TypeScript types and no styling to fight. Three things to check before you upgrade to version 2.0. The peer dependency moved to jQuery 3 and the build target to evergreen browsers, so a page still on jQuery 1 or 2 has to stay on the 1.5.x line. And note that the npm package name is not the name people search for, so pinning and imports both need the published name rather than the repository name. Finally, if you move the dropdown out of the document body with appendTo, turn on forceFixPosition as well, because the auto-positioning only runs in the default parent.
Frequently asked questions
How do I use jquery autocomplete from this project?
Install the published package, which is named devbridge-autocomplete rather than after the repository, and call the autocomplete method on a selector with an options object. The UMD bundle also registers an alias method on the global jQuery, and defaults are readable and writable on the defaults object, with setOptions available to change them on a live instance.
What does this plugin need at runtime?
jQuery 3.0 or newer, and nothing else. Version 2.0 dropped jQuery 1.x and 2.x, so the peer dependency is jquery at 3.0 or newer and the build targets evergreen browsers at ES2020. If you cannot upgrade jQuery, the project says to stay on the 1.5.x release line.
How does the plugin decide which jQuery versions work?
The manifest declares a peer dependency of jquery 3.0 or newer and installs jQuery 4 as a development dependency, and it also contains four npm overrides mapping jquery1 through jquery4 onto jQuery 4. So the only jQuery actually present in a checkout is version 4, and the compatibility range has to be verified rather than inferred from those overrides.
Why is my autocomplete dropdown mispositioned after I changed appendTo?
Auto-positioning only runs when the dropdown is appended to the document body, which is the default. Moving it elsewhere with appendTo also requires the target to have a positioned style, and setting forceFixPosition to true to make the plugin position it anyway. The dropdown height, z-index and container class also have fixed defaults you may need to override.
Does the plugin support accented characters in suggestions?
Not by default. The default lookup filter is a case-insensitive substring match, so you need to pass a custom filter that normalises both sides to find Cafe against Café. The documentation notes that the default formatter still highlights only exact case-insensitive matches, so an accent-folded match is listed but not highlighted until you also supply your own formatter.
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/tkirda-jquery-autocomplete)Star history chart for your README
[](https://hysenlabs.com/projects/tkirda-jquery-autocomplete)Was this useful?