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

warn - enableUndici option is unnecessary in Node.js v18.0.0 or greater. #42441

Closed
1 task done
BWBama85 opened this issue Nov 3, 2022 · 6 comments · Fixed by #42444
Closed
1 task done

warn - enableUndici option is unnecessary in Node.js v18.0.0 or greater. #42441

BWBama85 opened this issue Nov 3, 2022 · 6 comments · Fixed by #42444
Labels
bug Issue was opened via the bug report template.

Comments

@BWBama85
Copy link

BWBama85 commented Nov 3, 2022

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

    Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 18.12.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.0.2-canary.2
      eslint-config-next: 13.0.1
      react: 18.2.0
      react-dom: 18.2.0

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

Describe the Bug

When running npm run dev I get:

warn - enableUndici option is unnecessary in Node.js v18.0.0 or greater.

My next.config.js:

/** @type {import('next').NextConfig} */
const nextConfig = {
  experimental: {
    appDir: true,
  },
};

module.exports = nextConfig;

Expected Behavior

Not to see this error message. I do not have this option in my config.

Link to reproduction

n/a

To Reproduce

next

@BWBama85 BWBama85 added the bug Issue was opened via the bug report template. label Nov 3, 2022
ijjk added a commit that referenced this issue Nov 3, 2022
Fixes: #42441

## Bug

- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Errors have a helpful link attached, see `contributing.md`

## Feature

- [ ] Implements an existing feature request or RFC. Make sure the
feature request has been accepted for implementation before opening a
PR.
- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Documentation added
- [ ] Telemetry added. In case of a feature if it's used or not.
- [ ] Errors have a helpful link attached, see `contributing.md`

## Documentation / Examples

- [ ] Make sure the linting passes by running `pnpm build && pnpm lint`
- [ ] The "examples guidelines" are followed from [our contributing
doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
@ijjk
Copy link
Member

ijjk commented Nov 4, 2022

Hi this should be updated in v13.0.2 please update and give it a try!

@BWBama85
Copy link
Author

BWBama85 commented Nov 4, 2022

Still seeing it.

    Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 18.12.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.0.2
      eslint-config-next: 13.0.2
      react: 18.2.0
      react-dom: 18.2.0

This time I do not get the warn immediately after starting, but while loading pages.

Initial start:

PS C:\Users\bamas\OneDrive\Documents\My Backups\Development\nodejs\thewilsonnet.com> npm run dev

> thewilsonnet.com@0.1.0 dev
> next dev

ready - started server on 0.0.0.0:3000, url: http://localhost:3000
warn  - You have enabled experimental feature (appDir) in next.config.js.
warn  - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.
info  - Thank you for testing `appDir` please leave your feedback at https://nextjs.link/app-feedback

event - compiled client and server successfully in 665 ms (200 modules)

After loading a page:

PS C:\Users\bamas\OneDrive\Documents\My Backups\Development\nodejs\thewilsonnet.com> npm run dev

> thewilsonnet.com@0.1.0 dev
> next dev

ready - started server on 0.0.0.0:3000, url: http://localhost:3000
warn  - You have enabled experimental feature (appDir) in next.config.js.
warn  - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.
info  - Thank you for testing `appDir` please leave your feedback at https://nextjs.link/app-feedback

event - compiled client and server successfully in 665 ms (200 modules)
wait  - compiling /about/resume/page (client and server)...
event - compiled client and server successfully in 904 ms (395 modules)
warn  - `enableUndici` option is unnecessary in Node.js v18.0.0 or greater.
wait  - compiling /page (client and server)...
warn  - `enableUndici` option is unnecessary in Node.js v18.0.0 or greater.
event - compiled client and server successfully in 388 ms (399 modules)
warn  - `enableUndici` option is unnecessary in Node.js v18.0.0 or greater.
warn  - `enableUndici` option is unnecessary in Node.js v18.0.0 or greater.

@zenflow
Copy link
Contributor

zenflow commented Nov 4, 2022

I just upgraded to 13.0.2 (I had to do this because I just upgraded node from 16.x to 18.12.0 and needed the fix from #42382)

I am seeing the warnings during next build (it's mangled with the animated console output):

warn  - Linting is disabled
warn  - You have enabled experimental feature (appDir) in next.config.js.
warn  - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.
info  - Thank you for testing `appDir` please leave your feedback at https://nextjs.link/app-feedback

info  - Creating an optimized production build
info  - Compiled successfully
info  - Checking validity of types .info  - VS Code settings.json has been updated for Next.js' automatic app types, this file can be added to .gitignore if desired
info  - Checking validity of types
info  - Collecting page data .warn  - `enableUndici` option is unnecessary in Node.js v18.0.0 or greater.
info  - Collecting page data
[=   ] info  - Generating static pages (0/3)warn  - `enableUndici` option is unnecessary in Node.js v18.0.0 or greater.
warn  - `enableUndici` option is unnecessary in Node.js v18.0.0 or greater.
[==  ] info  - Generating static pages (0/3)warn  - `enableUndici` option is unnecessary in Node.js v18.0.0 or greater.
info  - Generating static pages (3/3)
info  - Finalizing page optimization

@ooyay
Copy link

ooyay commented Nov 8, 2022

image

still getting same warn here

node 19.0.1
next 13.0.2

@zenflow
Copy link
Contributor

zenflow commented Nov 8, 2022

@ooyay They fixed it in v13.0.3-canary.0

See https://github.com/vercel/next.js/releases/tag/v13.0.3-canary.0

You can use 13.0.3-canary.0 in your package.json or wait for the next official release (13.0.3)

@github-actions
Copy link
Contributor

github-actions bot commented Dec 9, 2022

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 9, 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.

4 participants