file-type VS nodegit

file-type is a lightweight library for checking file types based on the header. It’s designed to run in Node.js and browser environments and provides a simple way of detecting file types from Buffers, files on disk, streams, and Blobs.

In a react app, I want to import fileTypeFromBlob from file-type. The function is not actually being imported because it's only available in the browser. This is made clear in the docs, but it also comes up in this issue.

Is there no implementation of something like file-type in go?

I've also added file type detection so it can try to open the url in the correct app. This is done using the library file-type.

Main reasons are to give you more control over exactly what is uploaded, such as checking magic numbers for file types, instead of assuming they match their extension, or having more fine-tuned control over rate limiting.

I want instead focus on the file-type library. This library applies the magic numbers approach to the ArrayBuffer of the file for detecting its type. It works with a large amount of different file types.

In Git Consensus, we accept commits and parse out the address to create a mapping between them. In the unit tests, we can check the basic address parsing logic. But to actually test out the full user interactions of an OSS project onboarding to be a DAO and do token rewards for commits, we need to actually build a Git repo from the ground up - using JavaScript tools like nodegit to do so.

Interesting, I guess this would be how to use it in JS: https://github.com/nodegit/nodegit

nodegit Authentication has become the biggest prolem with this entire process! I have added a comment to Issue 1035 but I don't know if it will get much traction as it seems there have been several issues out there already.