Merge support for binary modules

[johnnyman727]

@allanca has done quite a bit of work on this already and has an outstanding PR on the original CLI. We need to get this merged into the Tessel 2 CLI and the remote server set up.

[johnnyman727]

@wprater Here's the order of operations:

• The CLI needs to iterate through node_module dependencies and find those with binary dependencies. You can do that either by finding a bindings.gyp or checking for nan or bindings in the package.json dependencies. Here is an example.
• Ping an S3 server to fetch each of the dependency binaries. I can set this up when you're ready or you can use a test server you have access to until this is about ready to merge. We'll need to figure out how to make the server accessible by all Team Members.
• Inject them into the CLI tarball. It will need to happen between when we locate the entry point to the project and when we deploy it.

Bonus Points:

• If the binary dependency is not on the server already, have the t2-cli send a request to another server to run t2-compiler to create that dependency and then save it on the S3 instance with the rest of the deps. Once it's done, inject that binary into the tarball like normal.

You'll need to to use the t2-compiler for creating binary dependencies to test with. Feel free to ping @tcr if you have any issues with that.

[rwaldron]

@wprater any updates?

[rwaldron]

I'm going to look at the deploy routines and see where I can expose the data needed for this

[rwaldron]

@johnnyman727 I've updated your list above to indicate items that function (which is only the first). The Third item is in progress, using dummy tarballs.

[johnnyman727]

👍

[Student007]

@johnnyman727, @tcr or @rwaldron when I use t2 compile I get a tgz what includes a folder Release containing binding.node

If I like to use a binary on the current implementation of the t2-cli to push/run code on the Tessel 2 - what is necessary to do with the result of the t2 compiler ?

I would assume, manually edit the package.json what is generated by t2 init and copy the tgz to ... ??
Was reading https://github.com/mapbox/node-pre-gyp#2-add-a-new-target-to-bindinggyp but I am still a little bit unsure and confused. Maybe someone could give me a hint.
Also for handling deeper dependencies. For instance the noble package for USB Bluetooth LE has a binary dependency bluetooth-hci-socket so I have to rework the node_package/noble/package.json and replace theoptionalDependencies: bluetooth-hci-socket by something like

{
      "target_name": "action_after_build",
      "type": "none",
      "dependencies": [ "<(module_name)" ],
      "copies": [
        {
          "files": [ "<(PRODUCT_DIR)/<(module_name).node" ],
          "destination": "<(module_path)"
        }
      ]
    }

does it work to manually use pre-compiled binaries or is the t2 run index.js --full not handling pre-compiled binaries the right way at the moment ?