Vue-dropzone: Unexpected token (1:1495)

[TuguldurJ]

When I upgraded to latest version, I've got an error now.
` ERROR in ./node_modules/vue2-dropzone/dist/vue2Dropzone.js 1:1495
Module parse failed: Unexpected token (1:1495)
You may need an appropriate loader to handle this file type.

!function(a,b){typeof exports==='object'&&typeof module!=='undefined'?module.exports=b():typeof`

[rowanwins]

Hi @TuguldurJ

Yeah unfortunately the last release didn't go well due to upgrading some dependencies, I'm currently working on a fix.

[Hiroshi-Tagami-789]

Here in Japan, we have the same problem.
We are hoping fixing it !!

[rowanwins]

Hi @TuguldurJ & @Hiroshi-Tagami-789

I've just released [email protected] - I think this resolves the issue (fingers crossed)

[TuguldurJ]

It still same as before. Please check it again :)

[rowanwins]

Here we go again, this time as 3.5.5-alpha.0

[Adan2JP]

@rowanwins
Thank you!
Your library passed for running yarn dev on my product.
LGTM.
but, I'm wondering. What cause this error happened ?

[Adan2JP]

@rowanwins
However, I confirmed vue2-dropzone doesn't happen error with yarn dev.
Would you update version information to 3.5.5 ?

[benrolfe]

Here we go again, this time as 3.5.5-alpha.0

When will this fix be released to master?

[rowanwins]

Hi @benrolfe

Have just published it as 3.5.5

[rowanwins]

Hi @Adan2JP

Basically the problem was caused by updating dependencies in #429 . Everything appeared to work, but for some reason the minification in particular caused issues. I'm now using terser instead of uglify, during the misfires I also tried butternut but that also caused some issues.

[TuguldurJ]

It works now.
@rowanwins Thank you!

btw, i've got a css issue which was fine in before.

[rowanwins]

Doh @TuguldurJ - in having to tweak the build tooling I had to adjust the approach used for CSS. Can you perhaps open a new issue specific to the css, and perhaps just double check that it's not the cache or anything like that...

[TuguldurJ]

@rowanwins ok let me check for issue.

[sanna-woo]

hi!
I can confirm the css problem (was fine before updating ...):

[rowanwins]

Hi @sanna-woo

Can you please open a new issue and perhaps describe your config.

Thanks