Closed ValiDrv closed 2 years ago
Hey @ValiDrv
I'm afraid this library hasn't been tested with the compat build. We have our own custom build script mainly because this library was created quite a while before other solutions existed such as Vite's Library Mode. Our intention is to migrate to that solution which might provide better compatibility with Vue's different builds and other libraries.
By the way, your version 0.13.1 fixed some paths or something, since it builds correctly.
Pretty sure it's something with the paths to the dist folder or something along those lines.
The only was I could build it before was with "vue3-google-map": "^0.13.0"
node_modules installed, and the source code downloaded somewhere else, plus vite resolve alias pointing to the source code (which was pointing to the node_modules install I think).
hmm this is odd. The only difference this time was that I built and published manually since the CI/CD pipeline failed to publish the new version for some reason after building. Haven't had time to investigate this but what it does is exactly the same as what I did locally. I'm closing this for now. If you encounter the issue again let me know.
When I downloaded the source, this time it had the dist folder. My worry is that next time your build works it might break...
I think there is something wrong in the
0.13.0
build. with Vue3, VIte and @vue/compat (upgrading app from vue2 to vue3)If I use
"vue3-google-map": "^0.13.0"
from npm I can't render the default example. (see errors bellow)But if I download the source and point the
vue3-google-map
alias to the downloaded/src
folder while"vue3-google-map": "^0.13.0"
is installed, the page renders correctly (except for the[Vue warn]: (deprecation WATCH_ARRAY)
warnings)If I only have the source, and no npm, i get errors about missing
vue3-google-map
...