Hi @baptistejamin , I know this is a very old issue at this point, and I'm sorry for that, but I've just merged #218 which resolved #138. If this is still of interest to you, could you please let me know whether v0.8.2 resolves this problem as well, as the comments on the other issue indicate it might?

I recently struggled with this exact same issue. Unfortunately, newer versions such as v0.8.2 or v0.9.0 didn't solve the issue for me. The changes proposed in this pull request do seem to work though.

For anyone struggling with this; as an easy workaround, I temporarily made changes to the distributed file ./dist/vue-leaflet.es.js, replacing the first line with the following four lines (inspired by Josh's post on StackOverflow):

import { watch as de, ref as c, provide as G, inject as h, h as z, onUnmounted as se, onBeforeUnmount as J, defineComponent as defaultDefineComponent, onMounted as O, markRaw as C, nextTick as f, render as Je, reactive as Ke, computed as x } from "vue";
const g = (obj) => defaultDefineComponent({...obj, compatConfig: {
  RENDER_FUNCTION: false,
}})

Be advised though as this is not a reliable solution! Hopefully the changes proposed in this PR will one day be merged into master, giving those who need to use @vue/compat a working version of vue-leaflet.

in the version 0.9.0 this issue still exists. Is this PR going to be merged?