Currently there's no centralized place to manage dependency versions. You can add version to import specifier: import * as mod from "https://esm.sh/PKG[@SEMVER][/PATH]"; See https://esm.sh/#docs for more info about how requests for imports are handled. But by default latest version is used, which is the case also for the Svelte runtime library that is dependency for pages that have JavaScript enabled components.
I propose that we add a centralized UI for managing dependency versions. Dependency versions should be locked to some version instead of using the latest one. That should be the case at least for generated sites to ensure that they keep functioning as expected even when library maintainers release breaking changes.
Currently there's no centralized place to manage dependency versions. You can add version to import specifier:
import * as mod from "https://esm.sh/PKG[@SEMVER][/PATH]";See https://esm.sh/#docs for more info about how requests for imports are handled. But by default latest version is used, which is the case also for the Svelte runtime library that is dependency for pages that have JavaScript enabled components.I propose that we add a centralized UI for managing dependency versions. Dependency versions should be locked to some version instead of using the latest one. That should be the case at least for generated sites to ensure that they keep functioning as expected even when library maintainers release breaking changes.