Tommy

+1 This would be great. I also have the same usages of insert.into("")/update.table("table"). So a bit of a pain migrating away from that right now.

You should not really have to worry about the refresh token? as the plugin is already handling it. Updating the access token accordingly. Meaning you just use that token correctly...

Hi, not quite sure. This is functionality from the downstream [keycloak-js](https://www.npmjs.com/package/keycloak-js) library

I haven't really tested this. But i would think that you wouldn't really have to convert it to javascript. It is to allow typescript to know that there is something...

@rkrajukhunt Have never tried before i'm afraid. Maybe someone else has any experience

> Have the same issue! Cannot get access to the instance of `$keycloak`. All examples are using Typescript but I want a plain javascript one! :( In templates you should...

We could probably make use of provide/inject so you could get it in the setup method. As a workaround you could probably also use `getCurrentInstance` https://v3.vuejs.org/api/composition-api.html#getcurrentinstance although not recommended.

Assuming your issue is related or maybe same project as @yaooooooooo? https://github.com/dsb-norge/vue-keycloak-js/issues/127

As previously mentioned in other issues we are keeping keycloak-js at the current version because of redhat-sso using said version. So it won't be updated until there is a redhat-sso...

@theolevisage yeah, it is indeed. So we can bump up the keycloak-js dependency. And won't need the workaround to support old format