-
Notifications
You must be signed in to change notification settings - Fork 3
https://api.typings.org queries return a 500 error #103
Comments
Nothing has been changed in years, and my initial take is that if it's down I won't be fixing this. It was initially set up on Heroku and they recent sunset the node.js instance it was built on, which may mean something has changed with the project. I've been maintaining it with my money, and unfortunately do not intend to donate my time right now. |
See also #102. Typings has been deprecated on NPM for over 3 years now. |
It looks like this is most likely caused by https://devcenter.heroku.com/changelog-items/2035, it looks like the API can no longer connect to the configured DB. I spent a little while trying to see if it was fixable without major work, but it doesn't appear to be. |
Ok, found a workaround by going through https://github.com/brianc/node-postgres/blob/master/packages/pg-connection-string/index.js and finding a way to set SSL without needing to rebuild the app, since the app build is deprecated by Heroku. This is resolved for now. Please migrate away from typings so I can save time and money and shut down the server 🙏 |
Thanks so much @blakeembrey. Really appreciate your help. Will migrate to @types asap. |
Thank you very much @blakeembrey it is resolved now, we have a couple of applications which are dependent on this, but we will try our best to migrate those applications one by one. Thanks again ! |
This may or may not help with migrating away from the API at least, but the way typings resolution was designed was that the registry just acted as a kind of symlink. You might be able to get away with replacing the registry entries with the |
I am no longer able to download type files from api.typings.org
https://api.typings.org/entries/dt/jasmine/tags/2.2.0%2B20160621224255
Returns 500 Internal Server Error
The text was updated successfully, but these errors were encountered: