Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

import('next').NextConfig has required generateBuildId property #27428

Closed
stefanprobst opened this issue Jul 23, 2021 · 1 comment · Fixed by #27443
Closed

import('next').NextConfig has required generateBuildId property #27428

stefanprobst opened this issue Jul 23, 2021 · 1 comment · Fixed by #27443
Labels
bug Issue was opened via the bug report template.

Comments

@stefanprobst
Copy link
Contributor

What version of Next.js are you using?

11.0.2-canary.20

What version of Node.js are you using?

14.17.2

What browser are you using?

firefox

What operating system are you using?

ubuntu

How are you deploying your application?

vercel

Describe the Bug

in the current canary version, next exposes a config type at import('next').NextConfig. however, currently this has a required generateBuildId property, which should not be there i guess. it also seems to be missing the eslint config fields.

Expected Behavior

the config type at import('next').NextConfig should not have required properties (and include all possible configuration options)

To Reproduce

// next.config.js
/** @type {import('next').NextConfig} */
const config = {
  reactStrictMode: true,
};

module.exports = config;
@stefanprobst stefanprobst added the bug Issue was opened via the bug report template. label Jul 23, 2021
@balazsorban44
Copy link
Member

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.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants