esbuild fails with - No loader is configured for ".node" files

[mattrochon]

Trying to build my project with esbuild, index.js throws errors for all of the binary targets.

[stefan-gorules]

Hi @mattrochon,

To resolve the above issue you would need to use .node loader. See: evanw/esbuild#1051. Let me know if this helps.

[mattrochon]

I have tried that solution but it is not able to resolve the files on deployment to a lambda function.
The plugin proposed there tries to load all of the binaries, even ones that havent been installed and fails.

Bit out of my depth on this bundling stuff but very much would like to be able to use the node engine in my lambda function.

[stefan-gorules]

@mattrochon What specific set-up are you using (e.g. aws starter template, esbuild template, etc.)?

[mattrochon]

no starter template, using the aws-lambda package

Build invoked like this:

I use other modules that have native .node files (prisma, for example) which totally work. I only just recently added gorules and it doesnt seem to handle it int he same way.

***edit

To add context, this configuration passes the build, but on deployment its not loading the .node files so i get an error that

new ZenEngine() is not a constructor.

[mattrochon]

I'm not sure how to get this to build properly using esbuild. Do you have any insight here?

[mattrochon]

ok, add

--external:@gorules/zen-engine

and make sure your node modules has the binary targets you need

and itll work

[stefan-gorules]

Thanks for sharing! I'll close the issue now.

[raymondKelly]

ok, add

--external:@gorules/zen-engine

and make sure your node modules has the binary targets you need

and itll work

@mattrochon I'm in a very similar position to yourself. Why would you mark zen-engine as an external module? Are you also copying that into the lambda? Would you mind sharing your esbuild config?

Thanks for any help you can provide

[tokict]

So, copy it in the lambda and exclude specific platforms used. If you do local seploy from mac, then exclude darwin one, and if you do it via GH actions, exclude the x64 one like so: