3 ms·
> We've been working on some updates that will allow Deno to easily import npm packages and make the vast majority of npm packages work in Deno within the next
by andrew_ 4y ago
> We've been working on some updates that will allow Deno to easily import npm packages and make the vast majority of npm packages work in Deno within the next three months.
This is really huge and will be a huge boost to the Deno ecosystem. On the other hand, I quite enjoyed that it wasn't jacked into NPM. There were reasonable alternatives like https://jspm.org/ https://jspm.org/. This is a big swing at Node and I'll be watching with maximum curiosity.
As an aside, the only thing preventing me from adopting Deno as my daily driver has been the lack of AWS Lambda support (requiring a lambda layer, slowing down cold starts). Would be great if they could leverage connections and advocate for native AWS support.
- alvis 4y agoWell. While there's no official AWS Lambda runtime, you can always use a custom image to use deno as a lambda function. Here is just one from the community https://github.com/hayd/deno-lambda https://github.com/hayd/deno-lambda
- andrew_ 4y agoAs I had mentioned, it requires using a Lambda Layer. See: https://github.com/hayd/deno-lambda/blob/2d90756a0f18b57f16e1a7f34cf9e5f69a90479a/example-aws-cdk/cdk/example-aws-cdk-stack.ts#L19-L23 https://github.com/hayd/deno-lambda/blob/2d90756a0f18b57f16e... Using your own image (i.e. without using the base AWS image with the layer) you'd get even worse cold start times.