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

"Using external babel" spam in Next 11.1 #27982

Closed
oBusk opened this issue Aug 11, 2021 · 2 comments · Fixed by #28017
Closed

"Using external babel" spam in Next 11.1 #27982

oBusk opened this issue Aug 11, 2021 · 2 comments · Fixed by #28017
Labels
bug Issue was opened via the bug report template.

Comments

@oBusk
Copy link
Contributor

oBusk commented Aug 11, 2021

What version of Next.js are you using?

11.1.0

What version of Node.js are you using?

14.17.5

What browser are you using?

Firefox

What operating system are you using?

Ubuntu (WSL)

How are you deploying your application?

N/a

Describe the Bug

In Next 11.1 the info - Using external babel configuration from /{path}/.babelrc message is printed repeatedly.

When running dev server in a pretty small typescript project, it was printed 8 times.

Expected Behavior

It is printed once when building or when dev server is first started.

To Reproduce

  1.  npx create-next-app
  2. In your new app, add a .babelrc containing;

    {
        "presets": [
             "next/babel"
        ]
    }
    
  3. Then run

    npm run build
    

My output is then

info  - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5
info  - Checking validity of types  
info  - Using external babel configuration from /{path}/.babelrc
info  - Using external babel configuration from /{path}/.babelrc
info  - Using external babel configuration from /{path}/.babelrc
info  - Using external babel configuration from /{path}/.babelrc
info  - Creating an optimized production build  
info  - Compiled successfully
info  - Collecting page data  
info  - Generating static pages (3/3)
info  - Finalizing page optimization 

Downgrading to next@~11.0.0 shows nothing about using the external config at all, which is probably not expected either.

@oBusk oBusk added the bug Issue was opened via the bug report template. label Aug 11, 2021
@timneutkens
Copy link
Member

Thanks for the report! Opened a PR here: #28017

@kodiakhq kodiakhq bot closed this as completed in #28017 Aug 12, 2021
kodiakhq bot pushed a commit that referenced this issue Aug 12, 2021
Fixes #27982



## Bug

- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Errors have 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 helpful link attached, see `contributing.md`

## Documentation / Examples

- [ ] Make sure the linting passes
@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 27, 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.

3 participants