Error when building using Webpack
See original GitHub issueHi @shershen08
Thanks for the amazing tool here, and everything works as it should. However, when I tried to bundle everything in Webpack
(I used Vue-cli
), the below error showed up.
ERROR in static/js/vendor.6534844124b38bd29711.js from UglifyJs
Unexpected token: operator (>) [./node_modules/vue-masonry/src/masonry.plugin.js:19,0][static/js/vendor.6534844124b38bd29711.js:41470,27]
I looked more in details into the above directory, it looks like the following line is causing the problem, but I can’t seem to find out why. Maybe you can discover something I missed here. Thanks.
const stringToBool = val => (val + '').toLowerCase() === 'true'
Issue Analytics
- State:
- Created 6 years ago
- Comments:23 (12 by maintainers)
Top Results From Across the Web
build error with webpack - Stack Overflow
I've tried installing different versions of babel and webpack with no luck. I'm following an old tutorial on youtube and I was wondering...
Read more >How I solved and debugged my Webpack issue through trial ...
When webpack bundles your source code, it can become difficult to track down errors and warnings to their original location.
Read more >next build fails with webpack error #25276 - GitHub
I'm using webpack 4 and started receiving this error today in my monorepo after updating next. Fixed it for now by using "next":...
Read more >Development | webpack
Using source maps. When webpack bundles your source code, it can become difficult to track down errors and warnings to their original location....
Read more >Error when attempting to package application using Webpack
1) Create new JET app with: ojet create web-app-navbar --template=navbar --typescript · 2) Build the JET app with "ojet build" · 3) Unzip...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@pingshunhuangalex you’re totally right. Doing it now. Thanks again for your time helping out with this issue!
I will merge and publish to NPM today.