Github reader support for npm-style semantic versioning includes

[mm-gmbd]

It would be great if Builder would respect npm-style SemVer rules for GitHub includes. This is really a precursor to something like spm (Squirrel Package Manager 😄 ), but it would help greatly in large projects where several libraries are included.

@include once github:name/repo/file.nut@^v0.3
@include once github:name/otherRepo/file.nut@>=v1.5.2

[deldrid1]

+1 for this.

In the interim, it would be great if Builder could at least warn you if you are including different revisions of the same file. Right now you get code bloat and confusion as both files are included, but the last included version takes precedence (even if it isn't the newest release)

@include once "github:owner/repo/file.nut@v1.0.5"

...

// From some other included file

@include once "github:owner/repo/file.nut@v1.0.3"