Marcin Cieślak

I think this software does not support so-called OpenSSL "engines" at all. You might want to try to use something like https://github.com/tpm2-software/tpm2-pkcs11 and then one of the Python's PKCS11 libraries...

@laurivosandi My first attempt to provide partial ed25519 is in https://github.com/wbond/oscrypto/pull/64 - but this is for OpenSSL only and @wbond is right in saying we should have this for other...

I'd say works as expected - https://sass-lang.com/documentation/modules/list#index says If $value appears multiple times in $list, this returns the index of its first appearance. You might want to use [@for](https://sass-lang.com/documentation/at-rules/control/for) instead.

You can deploy your binary directly with a proper name we expect into `vendor/linux-x64-57/binding.node` file and this should work. We don't support patterns in the names like this.

When running only one render process at a time (`process.env.MAX_SIMULTANEOUS_BUILDS` == 1) we are getting the following execution paths: (full log - https://gist.github.com/saper/75c8d334ada304005c9a26f3528c9ec9) * Thread 10 (LWP 102048 of process...

When running two builds at a time (`process.env.MAX_SIMULTANEOUS_BUILDS` == 2) we get the following executions paths: (full log - https://gist.github.com/saper/7c77ad6407cb24dde66dad2c39553de8) Thread # | source | LWP | dctx | importer...

Can we simplify the custom importer to some small function? How does it behave in case of an error?

Do you know how and who will be building binaries for OpenBSD?

We are getting requests like https://github.com/sass/node-sass/issues/2840#issuecomment-624358082 from folk who try to run some apps using node-sass on OpenBSD, please reconsider.

Thank you @glenn2223 for your patience! I'll check if my build machinery can build node-sass for electron as well.