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
[vite] Internal server error: Cannot overwrite across a split point #14
Comments
So far, I don't suffer the error and know nothing about it. But after reading the error stack, I think vue use magic-string to compile SFC file and throw the error during compiling time. So everywhere of the whole SFC file content may cause the error. If everything is fine while you don't using any decorator libraries, it should happened in type script code section. Try to separate ts code to a single file and import it, see if the error be fixed.
Due to the component class code is loaded from a ts file, SFC compiler may skip it. |
I advice you to contribute the issue to |
Thank you, I had a feeling but wanted to confirm first. :) I'll close this issue and see if I can dig up more information and/or a reproducible example and post a new issue to the Vue/SFC repository. |
If you create an issue about this, please @ me. thank you. |
@ruojianll I didn't yet have a chance to submit an issue, but someone else did! Here's the issue: And the same person also provided a PR to fix it here: |
@Dids Congratulations! It seems to work fine on all decorator repos. But why other people(and me ) didn't suffer your issue? |
Using Vue 3 + SFC + TypeScript + Vite, and I consistently get this error whenever I try to use either the now "deprecated"
vue-class-component
or this library (vue-facing-decorator
), which I've been using now, in hopes of fixing this.I'm using pretty much latest stable versions of everything, but have tried rolling back several versions, except it makes no difference.
Additionally, I'm on macOS + M1 Pro (arm64/aarc64), just in case that makes a difference.
So far I've been entirely unable to track down why this happens, and it only seems to happen in larger components, while smaller components seem to be fine, but I'll keep digging, removing code piece by piece, until it stops and see if I can track it down.
In the meantime, I just wanted to ask around to see if anyone else has ran into this, as Google is not returning any useful results for this particular error.
Here's the full error:
The text was updated successfully, but these errors were encountered: