Pkg: Spread operator is not suported

[thiagofernando]

Hi,
in my code i have this
module.exports = {...defaultConfig, ...environment};

when I try to compile I get the following message

Unexpected token

[ashking]

Yeah, am having the same issue too. I suspected it could be the node issue. But it looks like pkg issue. @igorklopov any idea why?

[jflayhart]

Not sure if this is a pkg issue per se. How are you transpiling ES6 -> ES5? Node supports some ES6 syntax, but not all, so which version of node are you using?

Personally, I use webpack to babelfy the code prior to using pkg to avoid these sort of things. I am able to use all ES6 standards with node and pkg this way as I utilize object spread liberally.

[ashking]

Don't think this is a pkg issue per se. How are you transpiling ES6 -> ES5? Node supports some ES6 syntax, but not all, so which version of node are you using?

Using the latest LST version v8.9.4.

Node v8.9.4 supports use of spread operator without need of transpiling the code. Not sure why pkg would not?

[jflayhart]

Not sure, maybe something in how the binaries are packaged... again, I use webpack/babel to compress/transpile my code and then run pkg.

[kalinkrustev]

Duplicate of #206

[ramiel]

I don't see why we should use babel/webpack to transpile code which doesn't need to be transpiled. In my backend only projects I carefully avoid to use unsupported syntax just not to install other dependencies as webpack/babel etc. This should be considered a pkg issue, since it should do any supposition about how a user organize his project.