Closed hammady closed 1 year ago
For the first point, we need to include dev dependencies when packaging the service. We are literally running dev commands from the deployed function.
@fayez-nazzal generation works perfectly on AWS! Many thanks for all your work so far!
AWS Lambda has limitations running
npm
commands, or probably commands in general (see below for the error when invoked on aws, it works perfectly fine locally). The original plan was to build the static site using a node function (JS API), not a shell command. The current implementation is a hack where it invokes a shell command from a node function. There are 2 pieces in this puzzle:package.json
files, the root one in the generator service and the one in the svelte directory. I hope there was a cleaner method in node, but we may need to get around by doing this.Error logs:
FYI, the file-system for lambda is read-only. The only writable location is /tmp. I am not sure what led to the creation of the above folder. It could be easily fixable from the npm command.