You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12-8Lines changed: 12 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,14 +47,18 @@ app.get('/', (req, res) => {
47
47
48
48
## 4.0.0 Goals
49
49
50
-
1. Improved API - Simpler for end user to use and configure; extensible without breaking backwards compatibility or hurting API
51
-
2. Node.js 8+ only - can upgrade dependencies to latest (Jest); can use latest syntax in source and tests; can use server.listening; future-proof for Node.js 10
52
-
3. Promise resolution mode by default? Requires benchmarking. Otherwise try callback with callbackWaitsForEventLoop=false (configurable by user); requires benchmarking. If context.succeed is still most performant, leave as default.
53
-
4. Additional event sources - currently only supports API Gateway Proxy; should also support Lambda@Edge (https://github.com/awslabs/aws-serverless-express/issues/152) and ALB; have had a customer request for DynamoDB; should make it easy to provide your own IO mapping function.
54
-
5. Multiple header values - can get rid of set-cookie hack
55
-
6. Configure logging - NONE, ERROR, INFO, DEBUG; also include option to respond to 500s with the stack trace instead of empty string currently
56
-
7. Improved documentation
57
-
8. Option to strip base path for custom domains (https://github.com/awslabs/aws-serverless-express/issues/86)
50
+
1. ✅ Improved API - Simpler for end user to use and configure; extensible without breaking backwards compatibility or hurting API
51
+
2. ✅ Node.js 8+ only - can upgrade dependencies to latest (Jest); can use latest syntax in source and tests; can use server.listening; future-proof for Node.js 10
52
+
3. 🗓 Promise resolution mode by default? Requires benchmarking. Otherwise try callback with callbackWaitsForEventLoop=false (configurable by user); requires benchmarking. If context.succeed is still most performant, leave as default.
53
+
4. 🗓 Additional event sources - currently only supports API Gateway Proxy; should also support Lambda@Edge (https://github.com/awslabs/aws-serverless-express/issues/152) and ALB; have had a customer request for DynamoDB; should make it easy to provide your own IO mapping function.
54
+
1. Added ALB; requires refactoring of common logic, additional tests, example refactor.
55
+
2. Need to add Lambda@Edge
56
+
3. Need to add example of doing custom resolver (DynamoDB)
57
+
5. ✅ Multiple header values - can get rid of set-cookie hack
58
+
6. ✅ Configure logging - default winston and allow customers to provide their own; include option to respond to 500s with the stack trace instead of empty string currently
59
+
7. 🗓Improved documentation
60
+
8. ✅ Option to strip base path for custom domains (https://github.com/awslabs/aws-serverless-express/issues/86).
61
+
9. 🗓 Update example to include optional parameter for setting up custom domain
logger.debug('Server isn\'t listening... Starting server. This is likely a cold-start. If you see this message on every request, you may be calling `awsServerlessExpress.createServer` on every call inside the handler function. If this is the case, consider moving it outside of the handler function for imrpoved performance.')
0 commit comments