(intermediate value)(...) is not a function error in code immediately following index.js from object-path

[ghost]

Since upgrading object-path to 0.11.8 this error started appearing.
I think it's because of the removed ; in index.js on 4f0903f#diff-e727e4bdf3657fd1d798edcd6b099d6e092f8573cba266154583a746bba0f346L306

I am only using index.js in my project, could be an issue in other files as well.

[mariocasciaro]

Hi Hajdi
Where that (function() { at the end is coming from? It's not from object-path right?

[ghost]

No, it's from another package I have. But the problem originates from object-path, because it's not properly closed with a ; (at least in index.js which I'm using)
See this issue: https://stackoverflow.com/questions/42036349/uncaught-typeerror-intermediate-value-is-not-a-function
Downgrading object path to 0.11.7 fixes the error.

The file you see has many plugins concatenated in a single app.js file, one of which is object-path's index.js

[ghost]

I think just adding a ; at

object-path/index.js

Line 320 in 4f0903f

})

would stabilize the package.

[ghost]

I realized that the problem only occurs because I minify my app.js file. Object-path works when included separately and not minified: https://jsfiddle.net/hajdi_k/Lge47nwv/ (look in resources)

I see a lot of resources on the net for issues with semicolons and minification. Also see this comment (on a completely different repo but similar issue) dalelotts/angular-date-time-input#21 (comment) .

I guess I can separate all files I concatenate with ; or a new line, before minifying.. My error now occured because index.js was followed by (function() { from another package.

It would be nice to not have to do this, because this occurs only on this package (so far). Others might be experiencing this issue as well and it's a bit difficult to debug.

Closing, since I can handle it when minifying.