Define MyProjectLambda construct that handles common patterns, add methods for optional functionality.
[0] https://docs.aws.amazon.com/prescriptive-guidance/latest/aws...
110 karma · joined February 9, 2023
Define MyProjectLambda construct that handles common patterns, add methods for optional functionality.
[0] https://docs.aws.amazon.com/prescriptive-guidance/latest/aws...
This is the eye opener for me, how is a startup justifying a re-write when they don't even have customers?
Unless you accidentally create the wrong branded type? Which is as likely as disordered arguments.
As you stated, tests should cover this case trivially, I don't see the value in added type complexity.
Can you expand on this? Error handling in middleware is pretty well documented.
And read release notes for everything you upgrade too.
Also they could have provided an actual error rather than letting it panic!
The extra parentheses is just habit from Prettier formatting :)
Jest and Mocha both do not support ESM very well out of the box and there is an expectation that you are using babel to transpile to CommonJS for everything to work nicely. (See Jest's _experimental_ support for ESM mocking!). Node.js is only starting to build out a testing framework, and it has a way to go yet until it has any level of feature parity with the established libraries.
Then you have the naive assumption that any package written in JS works with TS. Which is true, they do work, but the missing types will always lead you to look for a TS-first alternative. A good example of this is Joi vs Zod for validation, with the latter performing type inference based on your validation parameters, which is great. But it really does feel like you have a subset of a package ecoystem lurking on NPM.
I am not that confident Deno is the answer, but I would say those are my biggest frustration writing production grade JS/TS code today.
You have to do `['10', '10', '10'].map((val) => parseInt(val, 10));` to get the "expected" output. In addition, you should always provide `base` to `parseInt` otherwise it has it's own interpretation infered by the value you give it.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...