-
Notifications
You must be signed in to change notification settings - Fork 26
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
vue Uncaught TypeError: Cannot assign to read only property 'exports' of object '#<Object>' #6
Comments
Funny - you and I are doing the same work. Just ran in to the same problem. Of course... now I get a 404 error and the ads won't load on the page, but I don't think that's this components fault. That may be a service-worker issue. Darrynten - I just checked it looks like you fixed it here, but when downloading from npm the error is still present. Just fyi =) |
I am working with Vue and it is components fault. Revert your last commit. I did it and it worked |
@jamesmskelsey hi there, does the latest dev work for you but the npm one doesn't? |
@darrynten Yeah man, got the latest dev to work just fine. Heck, what I ended up doing was just manually changing the line that needed changed. When I downloaded it from npm, it was still giving the error from issue 3. |
Hi @jamesmskelsey, any chance of a pull request? Would be amazing ✨ |
hey @darrynten, I just installed the package and still can see this error because Currently, it looks like this:
|
Confirmed, this issue still on npm |
also confirming, still an issue with npm version. repo version works great. |
The way to get around this is to:
Done! |
@craigh411 Yes you are right, im my case I should do Take notice that you use |
@MitsuhaKitsune I'm glad it helped. I always use |
The code is ok. However you can mix require and export. You can't mix import and module.exports.
In your main.js replace this:
with this:
The text was updated successfully, but these errors were encountered: