Single source of truth for version

[dennisvang]

This creates a version string based on git tags during the build phase.
The version string is based on the latest tag and is always in git's long format, e.g. v1.2.3-0-gfc7760f if the latest tag is v1.2.3.
If the repo has no git tags (yet), we fall back on the abbreviated commit hash, e.g. fc7760f.

• removed name and version from package.json
• added gitDescribeVersion helper vite.config.ts to get the app version from git during the Vite build phase

Note that gitDescribeVersion runs git describe, synchronously, using child_process.spawnSync, and fails intentionally if the version string is empty.

fixes #47

[mihailefter]

Hi @dennisvang! I think that, when running npm run build, the container has no access to the .git directory, so it cannot get the version. Also, is the git binary present in the node image?
I also get the impression that we would start making use of tag versioning, or?

[dennisvang]

I also get the impression that we would start making use of tag versioning, or?

Yes, the release process uses git tags for versioning, same as for the fdp repo, etc.

[dennisvang]

[...] I think that, when running npm run build, the container has no access to the .git directory, so it cannot get the version.

@mihailefter Yes,good point. That was true for the npm run build call in the Dockerfile, because .git was still in .dockerignore.

I just removed .git from the .dockerignore so it is now included in the build context.
This should not be a problem, because only the build output is copied into the final image.

[...] Also, is the git binary present in the node image?

Yes, git is available in the image used for the dockerfile build stage.

[dennisvang]

@mihailefter I also updated the PR description.

[dennisvang]

@mihailefter do you think this is ready to be merged?

[mihailefter]

Hi @dennisvang! This can be merged, indeed.