Unexpected token error when using babel loader (vue webpack)
See original GitHub issueDescribe the bug
I am using webpack for vue (latest) and vue-agile ^1.1.0
. When I import VueAgile in one of my components as import { VueAgile } from 'vue-agile';
I receive an error (see screenshot) from the babel loader. Am I doing something wrong?
Screenshots
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Syntax Error: Unexpected token Babel / Vue / Typescript #959
I get the following error trying to compile .vue component with typescript: 66 | export default class Matching extends Vue { > 67...
Read more >Webpack vue-loader gives "unexpected token {" for single ...
I use Visual Studio 2017 + ASP.NET MVC (as API + one layout) + Vue.js + Webpack. .vue single-page component files are loaded...
Read more >Unexpected token ' : ' from babel-loader - Get Help - Vue Forum
Hello, I use vue-property-decorator and im trying to incoprorate babel to be able to use jsx (tsx) in my singel file components.
Read more >Unexpected token with babel-plugin-transform-vue-jsx-Vue.js
Coding example for the question Module build failed: SyntaxError: Unexpected token with babel-plugin-transform-vue-jsx-Vue.js.
Read more >babel-loader - webpack
You can also speed up babel-loader by as much as 2x by using the cacheDirectory option. This will cache transformations to the filesystem....
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
@lukaszflorczak no that is fine, I will try it another way. Thanks anyway!
Well, the solution is using the babel plugin “transform-object-rest-spread” without excluding node_modules folder… 😐