`serverless` configuration is untyped
See original GitHub issueWhat version of Next.js are you using?
11.1.2
What version of Node.js are you using?
16.9.1
What browser are you using?
Firefox
What operating system are you using?
GNU/Linux
How are you deploying your application?
next dev
Describe the Bug
The serverless
configuration as mentioned in the blog, here, can be appended to the next.config.js
file.
My next.config.js
file was this when initialized:
/** @type {import('next').NextConfig} */
module.exports = {
reactStrictMode: true,
};
As you can see, it takes types from import('next').NextConfig
, but the types doesn’t include serverless
.
Expected Behavior
It should be typed.
To Reproduce
Just create an app and see the types on next.config.js
yourself.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Variables - Serverless Framework
Variables allow users to dynamically replace config values in serverless.yml config. They are especially useful when providing secrets for your service to ...
Read more >Serverless Framework Deprecations
Serverless constructor was refactored to depend on service configuration being resolved externally and passed to its constructor with following options:.
Read more >AWS Lambda Guide - Serverless.yml Reference
The Serverless Framework documentation for AWS Lambda, API Gateway, EventBridge, DynamoDB and much more.
Read more >AWS Lambda Functions - Serverless Framework
Configuration. All of the Lambda functions in your serverless service can be found in serverless.yml under the functions property.
Read more >Service configuration validation - Serverless Framework
When the setting is not explicitly specified, serverless defaults to configValidationMode: warn . If you find this functionality problematic, you may also turn ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This has been deprecated https://nextjs.org/blog/next-12#breaking-changes
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.