3 ms·

I was dumb enough to use https://unpkg.com/vue https://unpkg.com/vue on my projects and now I have to deal with "Uncaught TypeError: Vue is not a constructor" t

• phil-martin 5y ago
  Same here, I wonder how many apps around the world silently stopped working today. It was my own fault for not self hosting or not pinning the version, but it was still a surprise!
  • sebazzz 5y ago
    Should unpkg have discouraged this and not offered unversioned urls at all?
• numbsafari 5y ago
  Folks shouldn't use unpkg.com. The only relevant discussion you can find regarding a privacy policy is a twitter thread that ends with the developer saying "I really should discourage adoption because it's getting too big." No dig on them, but, really... at some point we need to start doing a better job of owning this stuff.
  • hendry 5y ago
    I'm using https://cdn.jsdelivr.net/npm/vue@2.6.14 https://cdn.jsdelivr.net/npm/vue@2.6.14 now
  • feupan 5y ago
    Not sure I see the problem you’re talking about. The issue was using an unversioned URL, which is a user error and has nothing to do with unpkg (other than allowing it)
• tosh 5y ago
  Same here, this is how I found out about Vue 3 related: The mess we're in (a talk by Joe Armstrong) https://www.youtube.com/watch?v=lKXe3HUG2l4 https://www.youtube.com/watch?v=lKXe3HUG2l4 (yes, I know, I should have vendored the dependency in the first place)
• ThatPlayer 5y ago
  Same here. I think I noticed within an hour or two because I checked, but can see other people being bitten on it.
• pas 5y ago
  https://unpkg.com/vue@2.6.14/dist/vue.js?meta https://unpkg.com/vue@2.6.14/dist/vue.js?meta https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity https://developer.mozilla.org/en-US/docs/Web/Security/Subres...