Getting babel build errors with the next.js getting started example

Question

Following along the getting started example from ZEIT for next.js, I'm getting this error:

error  in ./pages/index.js

Module build failed: ReferenceError: [BABEL] /Users/Projects/nextDemo/pages/index.js: Using removed Babel 5 option: /Users/Projects/.babelrc.optional - Put the specific transforms you want in the `plugins` option

What is this error - is it trying to use my globally installed babel? Is there a version mismatch or an update I should be doing?

This is the basic steps I did to get here:

$ npm install next --save
$ mkdir pages

//pages/index.js:
import React from 'react'
export default () => <div>Hello world!</div>

Add a script to the package.json like this:
{
  "scripts": {
    "dev": "next"
  }
}

$ npm run dev

and the installed packages:

└─┬ [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  ├── [email protected]
  └── [email protected]

Community · Accepted Answer · 2020-06-20 09:12:55Z

0

It uses your .babelrc file from the parent directory because:

Babel will look for a .babelrc in the current directory of the file being transpiled. If one does not exist, it will travel up the directory tree until it finds either a .babelrc, or a package.json with a "babel": {} hash within.

Use "babelrc": false to stop lookup behavior.

edited Jun 20, 2020 at 9:12

CommunityBot

11 silver badge

answered Dec 30, 2016 at 10:02

Rudi

2,9851 gold badge14 silver badges18 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

MonkeyBonkey Over a year ago

shouldn't the next package have the correct babble configuration already?

Collectives™ on Stack Overflow

Getting babel build errors with the next.js getting started example

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related