Question: existing configuration and unexpected behavior

[COV-GIS]

What does this mean?

Thanks.

[jcfranco]

2.10.0 (see #8848) added a way to check the components version at runtime. It does so by 'stamping' the version onto a global calciteConfig variable when Stencil's global script executes. This warning message will be displayed if there is an existing version on the global config when stamping. We have an issue to revisit the message to provide better context.

Would you mind sharing more info about your use case? It might be useful for #9721.

[COV-GIS]

Thanks @jcfranco for explanation. I wasn't too concerned with the versions matching but definitely wanted to understand if there started to be issues. Not 100% on this but after some digging methinks it's because of vite/rollup and all the magic module optimization, bundling and loading. My only suggestion would be to not warn if the versions match.

[jcfranco]

Not 100% on this but after some digging methinks it's because of vite/rollup and all the magic module optimization, bundling and loading. My only suggestion would be to not warn if the versions match.

@COV-GIS Would you be able to share more details behind your use case? I started working on #9721 and was not able to reproduce this same-version warning with the calcite-components-examples repo. The version check happens at the global script level, which should be happening once, so there might be something else going on.

[COV-GIS]

Here you go @jcfranco: https://github.com/CityOfVernonia/vite-map-app