Dependencies like node-sass currently don't work out of the box. They need python2 and the nodejs headers to be symlinked in the right place so that they can build the extension from source.
Some other packages like gifcycle try to download pre-built binaries from the Internet (which fails because/thanks to the sandbox). It would be nice if the package could advertise those URLs in their metadata somehow.
Some other packages (like ???) probably ship with the pre-built binary embedded into the package. In that case we might want to run autopatchElf before running the npm postinstall hook.
This is more of a reminder for myself.
Dependencies like
node-sass
currently don't work out of the box. They need python2 and the nodejs headers to be symlinked in the right place so that they can build the extension from source.Some other packages like gifcycle try to download pre-built binaries from the Internet (which fails because/thanks to the sandbox). It would be nice if the package could advertise those URLs in their metadata somehow.
Some other packages (like ???) probably ship with the pre-built binary embedded into the package. In that case we might want to run autopatchElf before running the npm postinstall hook.