fix: use number type for memory limit

[kubukoz]

Which problem is this pull request solving?

The runtime type of the field is number, as per typeof, at least in netlify functions:serve (cli v8.1.4)

Checklist

Please add a x inside each checkbox:

• I have read the contribution guidelines.
• The status checks are successful (continuous integration). Those can be seen below. <- waiting on running the workflows

[eduardoboucas]

Thanks @kubukoz! That property is actually a string in production, but incorrectly typed in the CLI.

lambda-local, the runtime emulator used by the CLI, is setting it as a number here: https://github.com/ashiina/lambda-local/blob/e1fccdac895d4ca45804d48f1d1d79116eac1f06/src/lib/context.ts#L36. We'll try to get a PR to get that changed, otherwise we'll change it on the CLI side.

As a side note, may I ask if you're using this property for anything specific?

[kubukoz]

We're implementing a Scala-friendly API: typelevel/feral#89 <- currently using the numeric type

We get an exception when trying it out locally because of Scala.js's semantics - it seems to be more picky about types when converting from a foreign (.js) type.

[armanbilge]

We'll try to get a PR to get that changed, otherwise we'll change it on the CLI side.

Done in ashiina/lambda-local#218 and released in https://github.com/ashiina/lambda-local/releases/tag/release%2F2.0.1