G should not jump to end of file empty newline

Not sure if this is a bug or feature request but it's not quite consistent with default vim behavior, so posting it as a bug.
When using the G motion the cursor jumps to the last line of the file, however this includes an empty new line. The question of whether to render the numbers for the newline has come up as an issue with VSCode and they've allowed an option to not show it, however this motion still jumps to that line:

https://user-images.githubusercontent.com/74646/132346500-9c43360c-4701-4fd5-8961-be8e32a7e651.mov

Compare this to default vim, where no second line is rendered or selectable.

Whether or not the line should be selectable at all is one question, however I suspect that this extension may not have control over this. Barring that, at least this text motion should not jump to the "last line" but instead technically one line before. This would make it consistent with default vim. At least this could perhaps be an option.

Seems like a small issue but Prettier always inserts this EOL for compatibility with *nix commands, which is not so easy (and probably not a good idea) to override. For example having a default export always at the last line would be difficult to jump to easily when using Prettier.

Workarounds would also be appreciated :)

Start by reproducing the G motion in VSCodeVim with a file that ends in an empty newline, then trace the motion handling and compare it with default Vim. Done means G lands on the final non-empty line while preserving expected behavior for other files; add coverage for the trailing-newline case if the existing tests support it.