You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if it has anything to do with the Parse shutdown but my service started failing since yesterday because it couldn't get the Parse JS SDK from parsecdn.com. Did you guys shut that down as well? Moved stuff to cdnjs.cloudflare.com for now. Do you recommend a better cdn?
The text was updated successfully, but these errors were encountered:
Yes, ParseCDN was part of the Parse shutdown. For a while now, we've been encouraging users to switch to unpkg.com (formerly npmcdn). The npm packages are fully compatible with this service, and in my experience it's been a great host.
I don't know if it has anything to do with the Parse shutdown but my service started failing since yesterday because it couldn't get the Parse JS SDK from parsecdn.com. Did you guys shut that down as well? Moved stuff to cdnjs.cloudflare.com for now. Do you recommend a better cdn?
The text was updated successfully, but these errors were encountered: