Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Why vue dependent?
See original GitHub issueHi, thanks for the cool project. But why this is vue dependent? It would be better if you export Confetti to make it available for standalone usage.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Dependency injection in Vue: Advantages and caveats
Dependency injection is a design pattern in which classes are not allowed to create dependencies. Rather, they request dependencies from ...
Read more >Dependency Injection in Vue.js Applications
In this article, we take a look at what patterns exist in Vue.js applications to provide dependencies to components. We examine the advantages ......
Read more >Composition API: Dependency Injection - Vue.js
The first argument is the injection key. Vue will walk up the parent chain to locate a provided value with a matching key....
Read more >Dependency Injection with Vue 3 - DEV Community
The one way we can use or get the value from provide() is to use inject() . We'll import that also from @vue/runtime-core...
Read more >vue.js - VueJS dependent properties - Stack Overflow
There is a form with 3 fields,. Total Item (QTY); UNIT Price (Single Item); Total Price (All Items). The scenario is like this, ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
As people could already be relying on this as “vue-confetti” maybe we just pull out the Confetti part to a seperate repo and keep this as a Vue wrapper of some kind.
You’re right but its not a good practice to import something from under library’s src folder etc. Src folder should not ship into npm in the first place. It would be better if author export
Confetti.