Zac Rosenbauer

@sdras any updates here? this should resolve the CI issue.

FYI I added a quick fix that should resolve the issue.

@aleixmorgadas Added the PRs (I thought I reviewed more back in the day but guess not I think I just went and opened PRs on the repos with issues 😄)...

Also... I forgot to add unicorn 🦄

@zolagonano Employees of Google have contributed to the repository. This means that Google owns the contributions of said employees aka to relicense I need Google's approval (this is from the...

Google banned OSS License list -> [https://opensource.google/documentation/reference/patching#forbidden](https://opensource.google/documentation/reference/patching#forbidden) I could look at this one -> [https://creativecommons.org/licenses/by/4.0/](https://creativecommons.org/licenses/by/4.0/)

@sindresorhus any guidance here on the License issue above (I think thats the last piece here of this puzzle) **Short description of issue**: I originally licensed as MIT (my default)...

> > Only question I have is there a number of "TODOS" added and usually I link those to issues if I can, especially things like "remove in v5". >...

@climba03003 I saw this yesterday on Mongoose repo (everything is in JS) -> https://github.com/SamVerschueren/tsd Might be good idea to help us prevent regressions in the future of types etc. (no...

Not sure why builds fail as this is purely a documentation update.