-
-
Notifications
You must be signed in to change notification settings - Fork 133
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 cannot find toggle-button
#65
Comments
Sooo what stops you from including just a component again? Seems to pretty much work for everyone else 🤔 Try |
If I ref the raw component from src it fails to build with In any case I've had no trouble importing various vue components (like I worked around it by just copying the source into my local assets and importing the component from there, but that's not as nice as being able to use the NPM package. But, my build issues aside, I would guess that many people would rather import the component and declare it in their own components rather than have a global component declared via plugin install. /shrug Maybe just me though. |
@euvl Thanks for the great component. Probably this is more just a documentation issue. Most Vue component packages export a component by default not a plugin although the plugin is very nice. I think this could be solved by just adding a second short paragraph or sentence showing how to import it as a component since that is what many are used to. It wasn't hard but I did need to look in the source to find the path because it wasn't documented. |
Made a pull request #66 to document importing component directly. |
Hey @aldencolerain , thanks a lot for your PR. Merged 👍 |
No matter what I try, Vue doesn't seem to be able to find the component . I'm wondering if the issue is using the name when the plugin calls it
ToggleButton
. Trying didn't work either, for whatever reason my build just won't pick it up.Is there a reason to favor distributing this as a vue plugin rather than just a component? Since the plugin literally just declares the component, why not instead let the user import the
Button
component and then use it how they see fit? That way the end user doesn't have to have this component globally if they're not using it everywhere.The text was updated successfully, but these errors were encountered: