Element: [Bug, Report], NPM, run, build, Error

Created on 3 Jun 2017 · 30Comments · Source: ElemeFE/element

Element UI version

1.3.4

OS/Browsers version

Mac/safari

Vue version

2.3.3

Reproduction Link

https://jsfiddle.net/xryt9b4j/2/

Steps to reproduce

npm run build error
ERROR in static/js/vendor.e009106343d3b31cf28f.js from UglifyJs
Unexpected token punc «(», expected punc «:» [./~/element-ui/packages/col/src/col.js:23,0][static/js/vendor.e009106343d3b31cf28f.js:146795,10].

用npm run dev is Ok

What is Expected?

修复Bug

What is actually happening?

修复Bug

Source

subo-romens

👍2 👎1

Most helpful comment

module: {
    rules:[
       {
        test: /\.js$/,
        loader: 'babel-loader',
        include: [resolve('src'), resolve('test'),resolve('/node_modules/element-ui/src'),resolve('/node_modules/element-ui/packages')]
      },
   ]
}

it's works for me.

jackie19 on 29 Aug 2017

👍20 🎉2

All 30 comments

Translation of this issue:

Element UI version

1.3.4

OS/Browsers version

Mac/safari

Vue version

2.3.3

Reproduction Link

https://jsfiddle.net/xryt9b4j/2/

Steps to reproduce

NPM run build error

ERROR, in, static/js/vendor.e009106343d3b31cf28f.js, from, UglifyJs
Unexpected token punc ("expected punc", "[./~/element-ui/packages/col/src/col.js:23,0][static/js/vendor.e009106343d3b31cf28f.js:146795,10].":

With NPM run, dev, is, Ok

What is Expected?

Repair Bug

What is actually happening?

Repair Bug

element-bot on 3 Jun 2017

不要直接引入未编译的代码
不要乱加与 issue 无关的 demo

QingWei-Li on 3 Jun 2017

👎25 😕4 👍3 🚀1

I have the same problem. Is there a way to fix it?

CodeLookBook on 1 Aug 2017

I have the same problem. can somebody fix it?

callnothing on 23 Aug 2017

I have the same problem

ERROR in index.js?797e177ae8445502fcbd from UglifyJs Unexpected token punc «(», expected punc «:» [./~/element-ui/packages/col/src/col.js:23,0][index.js?797e177ae8445502fcbd:3929,10]

zhuzhengjing on 24 Aug 2017

same issue here . any fix?

legatoo on 28 Aug 2017

Keep Element from being processed by UglifyJS.

Leopoldthecoder on 28 Aug 2017

🎉2 👍2 😄1

module: {
    rules:[
       {
        test: /\.js$/,
        loader: 'babel-loader',
        include: [resolve('src'), resolve('test'),resolve('/node_modules/element-ui/src'),resolve('/node_modules/element-ui/packages')]
      },
   ]
}

it's works for me.

jackie19 on 29 Aug 2017

👍20 🎉2

@Leopoldthecoder Thanks, it resolves my problem.

fgcui1204 on 29 Aug 2017

@jackie19 very useful!

callnothing on 30 Aug 2017

@jackie19 thank you,it's useful!

wuyadream on 31 Aug 2017

Same error:
this error is occuring after updating it from older version 1.4.2 to newer version.

What is the real cause?

EmraanSiddiqui on 8 Sep 2017

not work, any update ??

dongxuan on 16 Oct 2017

@jackie19 work for me too

Justysxh on 23 Oct 2017

When I added this line:
[resolve('src'), resolve('test'),resolve('/node_modules/element-ui/src'),resolve('/node_modules/element-ui/packages')]
i've got this error:
"resolve is not defined"

exmozz on 1 Nov 2017

your version of uglify doesn't support es6 and needs to be updated. The latest version could be gained as separate plugin

webpack =< v3.0.0 currently contains v0.4.6 of this plugin under webpack.optimize.UglifyJsPlugin as an alias. For usage of the latest version (v1.0.0), please follow the instructions below. Aliasing v1.0.0 as webpack.optimize.UglifyJsPlugin is scheduled for webpack v4.0.0

Please refer to https://webpack.js.org/plugins/uglifyjs-webpack-plugin/

Once you will install v1.0.0 you will be able to build it

Daeghun on 1 Nov 2017

👍2

@Daeghun Thank you, it's helped.

exmozz on 1 Nov 2017

resolve a function that you need to customize
like this:
function resolve (dir) {
return path.join(__dirname, '..', dir)
}

@exmozz

Justysxh on 2 Nov 2017

@Daeghun should every one update the uglify plugins?

weituotian on 25 Nov 2017

兄弟，我也遇到这样的问题，可以帮下忙嘛 @QingWei-Li

FAKER-A on 6 Dec 2017

是不是element不能在浏览器用？

weituotian on 6 Dec 2017

是在打包的时候出现问题

FAKER-A on 6 Dec 2017

我看了一下 element ui 的这个文件语法没有被转换成es5

FAKER-A on 6 Dec 2017

我试了上面的方法解决不了很难过

FAKER-A on 6 Dec 2017

我用的webstorm, 直接写一个组件的标签的时候编译器会自动的帮你import某个单独的组件，而且会直接在export default里面的components里添加进去，把这两部分删掉就不会报错了，就是和 @QingWei-Li 说的一样，你引入了未编译的代码，所以才会报这个问题 @FAKER-A

yusphy45 on 24 Jan 2018

👍3 👎1

后来在code review的时候发现是有个实习生直接引用了没有打包的组件的问题

feijuncheng on 17 Apr 2018

@yusphy45 我也出现了这个问题，看了你的评论果然是webstorm单独引入了组件，去掉之后就好了，感谢。

shady-xia on 25 Apr 2018

我的问题是和@yusphy45 一样的，都是webstorm引入了组件的source code造成的，谢谢。不知道为什么 @weituotian 会给 👎 ....

nosus on 31 May 2018

终于解决了，注意node_modules前边没有/。

{
    test: /\.js$/,
        use: 'babel-loader',
    // exclude: /node_modules/,
    include: [
        resolve('src'),
        resolve('test'),
        resolve('node_modules/element-ui/src'),
        resolve('node_modules/element-ui/packages'),
        resolve('node_modules/vue-echarts-v3')
    ]
},

发现~vue-echarts这个组件也会有这个问题。。。