feat: expose version numbers
See original GitHub issueWe should make sure that the version number from the package.json
is exposed in client and server. For the server that could just mean to print it out at startup. For the client it would we good to see it somewhere or at least to be able to retrieve it via devtools quickly.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Expose XenTools version numbers in data model and UI #2650
Expose XenTools version numbers in data model and UI #2650 ... field in the data model so that XenTools version numbers may be...
Read more >How to do version numbers? [closed] - Stack Overflow
major - First release is 1 and then when we introduce major new features or changes so significant they are not backwards compatible...
Read more >Feature Toggles (aka Feature Flags) - Martin Fowler
Expose current feature toggle configuration. It's always been a helpful practice to embed build/version numbers into a deployed artifact and expose that ...
Read more >macOS version history - Wikipedia
macOS retained the major version number 10 throughout its development history until the release of macOS 11 Big Sur in 2020; releases of...
Read more >Version vs VersionSuffix vs PackageVersion: What do they all ...
In this post I look at the various version numbers you can set when ... The file version is literally the version number...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
How about looking into other apps to figure out how they do it? There’s probably a best practice already.
Merged with #519