RJR
Convex Community3y ago
7 replies
RJ

esbuild failure: No loader is configured for ".node" files

I just added a Node action and tried to deploy it to my dev environment, and observed the following error:

✘ [ERROR] No loader is configured for ".node" files: node_modules/ssh2/lib/protocol/crypto/build/Release/sshcrypto.node

    node_modules/ssh2/lib/protocol/crypto.js:30:20:
      30 │   binding = require('./crypto/build/Release/sshcrypto.node');
         ╵                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

✘ [ERROR] No loader is configured for ".node" files: node_modules/cpu-features/build/Release/cpufeatures.node

    node_modules/cpu-features/lib/index.js:3:24:
      3 │ const binding = require('../build/Release/cpufeatures.node');
        ╵                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
✖ esbuild failed: Error: Build failed with 2 errors:
node_modules/cpu-features/lib/index.js:3:24: ERROR: No loader is configured for ".node" files: node_modules/cpu-features/build/Release/cpufeatures.node
node_modules/ssh2/lib/protocol/crypto.js:30:20: ERROR: No loader is configured for ".node" files: node_modules/ssh2/lib/protocol/crypto/build/Release/sshcrypto.node


I'm guessing this has something to do with the ssh2-sftp-client package, which I haven't used before and which is a dependency of this particular action.
Was this page helpful?