Replies: 1 comment
-
same issue. any solution? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm using v10.2.7 for everything...
I have autocomplete working in a simple script that uses a downloaded autoComplete.js directly. I want to use the same code in an app with dependencies managed by npm, and bundled by grunt.
However, the initializer in my direct (working) version:
which calls the following constructor on line 614 in autoComplete.js:
Does not work in my bundled app:
because it appears to call a completely different constructor in autocomplete.js/src/standalone/index.js:
The javascript console chokes on
options
being null.I can't find a corresponding
function autoComplete(config)
in the npm version. What am I missing? All of the usage examples on https://tarekraafat.github.io/autoComplete.js show code that expects a single config object for the constructor.I'd love to use this package- it's so sleek! Thanks in advance!!!
In both cases, my config objection (autocomplete_config) is:
Beta Was this translation helpful? Give feedback.
All reactions