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.
Vuelidate/Validators v2 implicit dependency on Vue - JSPM module broken
See original GitHub issuevuelidate@next and validators@next package.json don’t declare their dependency on Vue 3. (vuelidate only declares it as one of its devDependencies)
As a result JSPM is unable to correctly create a working module. This can clearly be seen by comparing:
vue-router@4 (working - vue resolved to import "/npm:vue@3")
vuelidate@2 (broken - vue resolved to import "/npm:vue!cjs" )
validators@2 (broken - vue resolved to import "/npm:vue!cjs")
Here is a codepen that illusrates the issue. Would be great to push out alpha 1 to npm with this fix.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I think we could move it to peerDependencies right?
Hey, I’ve never used those services, so sorry bout that.
I suppose Vue 3 would have to be a dependency, as we use it’s composition API functions, correct?