Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

feat: expose version numbers

See original GitHub issue

We 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 GitHub Comments

1reaction

cburgdorfcommented, Sep 22, 2017

How about looking into other apps to figure out how they do it? There’s probably a best practice already.

0reactions

d3lmcommented, Sep 24, 2017

Merged with #519

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...

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...

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 ...

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...

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...