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.
HTTPError 302 after regular translation
See original GitHub issueAfter a few successful translates start to fail with warnings:
node index.js { HTTPError at translate (C:\Users\User\Desktop\node_test\node_modules\@k3rn31p4nic\google-translate-api\src\index.js:143:19) at process._tickCallback (internal/process/next_tick.js:68:7) name: 'HTTPError', statusCode: 302, statusMessage: 'Found' }
index.js:
translate(articleRU, { from: 'ru', to: 'bg' }).then(res => { console.log(res.text); }).catch(err => { console.error(err); });
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:8 (5 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
Nope. As this isn’t an official API, we don’t know about their rate limits.
Closing it as it has become stale. Feel free to reopen if you’re still facing the issue and have reproduction steps.