WIP: feat(versionpage): added version page for static and SSR

[KevinDanikowski]

added version page Fixes #108

[amclin]

I'm not seeing any version info being written out in this example.

I would expect to see:

• git commit hash
• git branch name
• git tag (if the current version has a tag) and/or the version number retrieved from package.json

[KevinDanikowski]

I'm not seeing any version info being written out in this example.

I would expect to see:

• git commit hash
• git branch name
• git tag (if the current version has a tag) and/or the version number retrieved from package.json

Excellent point, I wasn't sure what should be included so I just stuck with some environment and app info. I agree that the information you just suggested should be included. I will add that.

[KevinDanikowski]

FYI to add branch info, this is the code at a minimum I would need to add. This gets the branch name:

const find = require('findup-sync')

function gitHeadPath(cwd) {
  const filepath = find('.git/HEAD', { cwd: cwd || process.cwd() });
  if (!fs.existsSync(filepath)) {
    throw new Error('.git/HEAD does not exist');
  }
  return filepath;
}

function parseBranch(buf) {
  const match = /ref: refs\/heads\/([^\n]+)/.exec(buf.toString());
  return match ? match[1] : null;
}

console.log(parseBranch(fs.readFileSync(gitHeadPath(process.cwd()))))```

Which I got from https://github.com/jonschlinkert/git-branch/blob/master/index.js , but i wouldn't import directly because it isn't currently maintained and would thus be a vulnerability, better to bring it in house. 

[amclin]

There's an NPM module that makes it easy to get the details without having to parse them from the filesystem yourself:
https://www.npmjs.com/package/git-repo-info

[KevinDanikowski]

@amclin as long as you sign off on it i have no issue using that. so i'll use that one.

[amclin]

@KevinDanikowski yes, please use a library for reading git properties. Also, let's be careful about displaying environment variables, as protected values like security tokens may come from the environment. It would be better to only explicitly list specific properties.

[amclin]

@KevinDanikowski yes, please use a library for reading git properties. Also, let's be careful about displaying environment variables, as protected values like security tokens may come from the environment. It would be better to only explicitly list specific properties.

Currently using git-user-name in the generator to retrieve the user name. There's similar small libraries recommended for other git properties: https://www.npmjs.com/package/git-user-name

I'm ok with either using 1 library with multiple git functions, or a library per function if they're single-function libraries