The premise that you can (and should!) write production-ready serverless functions in Scala targeting JavaScript may be a surprising one. If this appeals to you, please contribute feature requests, ideas, and/or code! Why go feral? For the tooling of your choice, follow their instructions for deploying a Node.js Lambda using the contents of the target/scala-2.13/npm-package/ directory.Īs the feral project develops, one of the goals is to provide an sbt plugin that simplifies and automates the deployment process.If you have multiple, you will need to select the one to deploy using Compile / mainClass := Some('my.lambda.handler'). Note that you can currently only have one Lambda per sbt (sub-)project. Run sbt npmPackage to package your Lambda for deployment.yourLambdaName is the name of the Scala object you created that extends from IOLambda.index refers to the index.js file containing the JavaScript sources for your Lambda.The handler for your Lambda is index.yourLambdaName.The runtime for your Lambda is Node.js 18.To deploy a Scala.js Lambda, you will need to know the following:

For example you can use the Lambda console, the SAM CLI, or the serverless framework. There are several options to deploy your Lambda. Please refer to the examples for a tutorial. LibraryDependencies + = 'org.typelevel ' %%% 'feral-lambda-cloudformation-custom-resource ' % '0.2.1 ' LibraryDependencies + = 'org.typelevel ' %%% 'feral-lambda-http4s ' % '0.2.1 ' LibraryDependencies + = 'org.typelevel ' %% 'feral-lambda ' % '0.2.1 ' // Optional, specialized integrations, available for both JS and JVM AddSbtPlugin( 'org.typelevel ' %% 'sbt-feral-lambda ' % '0.2.0 ') // in plugins.sbtĮnablePlugins( LambdaJSPlugin) // in build.sbt // JVM setup

Feral cats download