-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected token: < #64
Comments
@CraigHarley Are you able to post a repo with a reproduction? |
I have a similar problem. I don't know which of the several moving parts is creating this problem so I opened an issue here: vuejs-templates/webpack#1335 As I said, I don't know if this is a webpack issue, vue-jest issue, jest issue, vue-test-utils issue, babel issue, etc... issue but any help would be really appreciated. Thanks |
The issue is that Jest is not using vue-jest to transform the SFC. If you're seeing this issue, it's likely that your configuration is incorrect. For example, it could be caused by the regex you're using in |
I have just started learning Vue recently by following this post: https://medium.com/cleversonder/from-zero-to-hero-with-vue-advanced-components-parcel-dev-tools-fab980a62259 I have encountered the similar issue. As parcel complaints the tag is not valid in the vue file. The completed source code for the tutorial by https://medium.com/@wesharehoodies is working from: However, if I delete the package-lock.json, delete the "node_modules" folder, and reinstall all packages again from package.json via "npm install", then the error occurs. Therefore, it seems some of the dependent packages have broken the build process. |
I'm almost certain it's something to do with the way babel is set up but can't seem to put my finger on it. The component is being pulled into the test but it's not actually running vue-jest on it, or so it seems.
This is the error
.babelrc
relevant package.json:
test looks like this:
Not sure what I'm missing here or if it's a bug with using laraval mix.
The text was updated successfully, but these errors were encountered: