You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use git SHA for our versions across our apps, and pass those versions to third-party analytics services like Datadog. Several of these providers can be largely configured as static <script> tags in our app.html, but we'd like to be able to include the current version as well.
Describe the proposed solution
We're passing the version string as recommended in the version docs and would like if that version string was available as an HTML placeholder, e.g. %svelte.version%.
Alternatives considered
We've looked at doing our own HTML templating as part of hooks.server, as well as duplicating the version string into PUBLIC_VERSION which we could then access via %svelte.env.PUBLIC_VERSION% but if it's reasonable/straightforward to propagate the version via template placeholders it would be great ergonomics
Importance
nice to have
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Describe the problem
We use git SHA for our versions across our apps, and pass those versions to third-party analytics services like Datadog. Several of these providers can be largely configured as static
<script>
tags in ourapp.html
, but we'd like to be able to include the current version as well.Describe the proposed solution
We're passing the version string as recommended in the version docs and would like if that version string was available as an HTML placeholder, e.g.
%svelte.version%
.Alternatives considered
We've looked at doing our own HTML templating as part of
hooks.server
, as well as duplicating the version string intoPUBLIC_VERSION
which we could then access via%svelte.env.PUBLIC_VERSION%
but if it's reasonable/straightforward to propagate the version via template placeholders it would be great ergonomicsImportance
nice to have
Additional Information
No response
The text was updated successfully, but these errors were encountered: