Skip to content
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

Computed property "title" is already defined in Props. #449

Closed
roelVerdonschot opened this issue Feb 22, 2023 · 5 comments
Closed

Computed property "title" is already defined in Props. #449

roelVerdonschot opened this issue Feb 22, 2023 · 5 comments

Comments

@roelVerdonschot
Copy link

Describe the bug
I'm getting the Vue warning: Computed property "title" is already defined in Props.

Desktop (please complete the following information):
"@fortawesome/vue-fontawesome": "^3.0.3",
"vue": "^3.2.0",
"vite": "^4.0.0",
Scherm­afbeelding 2023-02-22 om 11 42 20

@jasonlundien
Copy link
Member

@roelVerdonschot ---

Do you have a reproducible test case we can look?

@TomDeSmet
Copy link

I have this issue as well. But I have no idea what is causing it.
I'm using:

"vue": "^3.4.21",
"vite": "^5.1.6",
"@vitejs/plugin-legacy": "^5.3.0",
"@vitejs/plugin-vue": "^5.0.4",
"@fortawesome/fontawesome-free-regular": "^5.0.13",
"@fortawesome/fontawesome-svg-core": "^6.5.2",
"@fortawesome/free-solid-svg-icons": "^6.5.2",
"@fortawesome/vue-fontawesome": "^3.0.6",

Making a reproducable test case is not easy to di I fear.

@jasonlundien
Copy link
Member

jasonlundien commented Jul 24, 2024

@TomDeSmet ---

Is there a repo or test repo you could share that has this warning ?

@TomDeSmet
Copy link

Unfortunately no, it's in a large codebase with strict security. I'll try to do some tests and figure out as much as possible.

@TomDeSmet
Copy link

I cannot reproduce it in sandbox mode and I have no idea when it actually triggers. The Vue warning is not very clear on that.

But it looks to me like it only happens in Vite dev mode. I can't reproduce it after a build and running Vite preview.
It seems to trigger whenever I make a change in some codebase that uses <font-awesome-icon> that makes Vite reload its HMR and then the shit hits the fan for some reason.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants