-
Notifications
You must be signed in to change notification settings - Fork 12.2k
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
v6 Named export 'faDiscord' not found #18677
Comments
Hi! Thanks for being part of the Font Awesome Community. @robmadole since this only happens in development and it is related to Vue 3, is it possible that the issue belongs to the vue-fontawesome package? |
Same boat as @mhatvan, I am using sveltekit and pretty much got that same error. If I remove an icon, it just complains about the next one. |
The faBackpack, faBuildings, and faComputerClassic are also missing. |
Can anyone provide a reproducible example for me? That would help a ton. |
To clarify, it's fine during development, it only happens when you come to bundle for production |
Hi @alexcroox --- I am not able to reproduce this build error, and perhaps could use your help if you have a few minutes to spare here or there.
So if you get a chance, could you take a look and let me know what I am missing. |
I get the same problem, with a bunch of icons, as well as the I uploaded it in a repo that is stripped clean of anything but FontAwesome, you can find it here. |
@fabianmossberg --- |
@jasonlundien: One more thing. It works perfectly if I do the following: Edit the the following files:
By adding this:
As suggested by this PR But I assume that those files are generated by some other private repo, and that the change that is needed would be done there. |
A workaround until the packages are shipped as esm is to fix it in the vite config. In SvelteKit, edit |
All we are going to focus the conversation about |
Describe the bug
Vue 3
Oddly it works during development, just not build (using Vite)
Screenshots
Bug report checklist
The text was updated successfully, but these errors were encountered: