Nathan Youngman

#36 may be slightly related

This appear to only be an issue when the autocomplete field is inside a ``.

I was seeing this warning in the Chrome console after upgrading to v2.0.1 using the latest Vue 2.6.11 and Vuetify 2.2.12. However, the `npm install --no-cache` [tip](https://github.com/MadimetjaShika/vuetify-google-autocomplete/issues/91#issuecomment-570029705) worked! Thanks.

Spoke too soon. The warning is back. May have disappeared for some other reason, as I'm still in the midst of updating Vuetify (the warning was there before I started).

Any plans to split off the ActiveRecord dependencies as some sort of plugin?

I can confirm that it works fine in this case (with a NestaCMS/Sinatra app). I'm not 100% sure whether or not AR is loaded/impacting the memory footprint.

Just fyi, we're no longer using Oink in development.

Andrew, I found the problem. I had placed my .bbprojectd file in my Dropbox instead of the project folder like I normally would. Thought I might share it with myself....

Do you have "documents to track" set to all? That bit me the first time.

That would make sense to me. A ended up not using PeepOpen for quite some time because it wasn't finding everything TextMate was finding. Then I found the silly **"documents...