最新消息:Welcome to the puzzle paradise for programmers! Here, a well-designed puzzle awaits you. From code logic puzzles to algorithmic challenges, each level is closely centered on the programmer's expertise and skills. Whether you're a novice programmer or an experienced tech guru, you'll find your own challenges on this site. In the process of solving puzzles, you can not only exercise your thinking skills, but also deepen your understanding and application of programming knowledge. Come to start this puzzle journey full of wisdom and challenges, with many programmers to compete with each other and show your programming wisdom! Translated with DeepL.com (free version)

javascript - Babel-Loader Syntax error on npm run build - Stack Overflow

matteradmin6PV0评论

I am not very strong with webpack and am trying to update webpack from V3 to V4 and have managed to update my webpack config to the point where its not throwing depreciation errors at me, but I am now stuck on a syntax error from babel-loader:

      Module build failed (from ./node_modules/babel-loader/lib/index.js):
      /path/react/node_modules/schema-utils/dist/util/hints.js:16
      const currentSchema = { ...schema
      SyntaxError: Unexpected token ...

In my webpack config I have this:

         test: /\.(js|jsx)$/,
            use: [
              {
                loader: 'babel-loader',
                options: {
                  presets: [
                    '@babel/preset-env',
                    '@babel/preset-react',
                    {
                      plugins: [
                        '@babel/plugin-proposal-class-properties'
                      ]
                    }
                  ],
                  pact: true,
                  cacheDirectory: false, // @todo: legacy option: true
                },
              }
            ]

and I am using the following versions:

 "@babel/core": "^7.1.6",
 "@babel/plugin-proposal-class-properties": "^7.8.3",
 "@babel/preset-env": "^7.1.6",
 "@babel/preset-react": "^7.0.0",
 "babel-loader": "^8.0.4",

I have tried multiple times with diffent versions of babel but always end up at this message. Can anyone see any obvious mistakes I am making?

I am not very strong with webpack and am trying to update webpack from V3 to V4 and have managed to update my webpack config to the point where its not throwing depreciation errors at me, but I am now stuck on a syntax error from babel-loader:

      Module build failed (from ./node_modules/babel-loader/lib/index.js):
      /path/react/node_modules/schema-utils/dist/util/hints.js:16
      const currentSchema = { ...schema
      SyntaxError: Unexpected token ...

In my webpack config I have this:

         test: /\.(js|jsx)$/,
            use: [
              {
                loader: 'babel-loader',
                options: {
                  presets: [
                    '@babel/preset-env',
                    '@babel/preset-react',
                    {
                      plugins: [
                        '@babel/plugin-proposal-class-properties'
                      ]
                    }
                  ],
                  pact: true,
                  cacheDirectory: false, // @todo: legacy option: true
                },
              }
            ]

and I am using the following versions:

 "@babel/core": "^7.1.6",
 "@babel/plugin-proposal-class-properties": "^7.8.3",
 "@babel/preset-env": "^7.1.6",
 "@babel/preset-react": "^7.0.0",
 "babel-loader": "^8.0.4",

I have tried multiple times with diffent versions of babel but always end up at this message. Can anyone see any obvious mistakes I am making?

Share Improve this question asked Jun 2, 2020 at 12:51 Thomas AllenThomas Allen 8118 gold badges18 silver badges33 bronze badges
Add a ment  | 

1 Answer 1

Reset to default 5

The SyntaxError: Unexpected token ... implies that your node isn't transpiling ES6. Have you upgraded node/npm to relatively new versions?

Also, if you're changing versions, I would suggest deleting your node_modules folder and package-lock.json file before running npm install again.

Post a comment

comment list (0)

  1. No comments so far