Jan Manuel Schlieper
Jan Manuel Schlieper
I too find this behavior highly irritating! Especially when I even specify a commit in the regular package.json, I expect yarn to install exactly that commit! Cheers!
Hey! I have the same problem on OSX. It is node v0.12.13, which is due to working in an meteor environment. It seems to run on my debian system though....
Whats up with this? Why has this been broken. I noticed the suggested fix is the behaviour of 1.3.3
Hey! I have some cases where I dynamically define some components in the created() hook. `created(){ this.$options.components.textarea = {...some component defintion... }` This does also not work when using reserved...