Why not start the NPM server?

Warning: count(): Parameter must be an array or an object that implements Countable in /home/styllloz/public_html/qa-theme/donut-theme/qa-donut-layer.php on line 274
0 like 0 dislike
Make bot for telegram, at the beginning faced with the problem of the following nature.
Does not start the local server with the following error:
[nodemon] 1.17.3 [nodemon] to restart at any time, enter `rs` [nodemon] watching: *.* [nodemon] starting `node index.js` node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated. In the future, you will have to enable it yourself. See https://github.com/yagop/node-telegram-bot-api/issues/319. module.js:643:30 error: [polling_error] {"code":"EFATAL","message":"EFATAL: Error: getaddrinfo ENOTFOUND api.telegram.org api.telegram.org:443"}

Error bad Google.
All that contains my index.js:
const TelegramBot = require('node-telegram-bot-api') const TOKEN = '///' const bot = new TelegramBot(TOKEN, { polling: true }) bot.onText(/\\/start/, msg => { console.log(msg) })

Suspected that the problem is the massive locks, was trying to use a free proxy for npm:
proxy= https-proxy=
from hidemy.name.
However, the number of dead. Pomogite people!!!
by | 525 views

1 Answer

0 like 0 dislike
In General, the solution found by myself. The most basic, downloaded the one a VPN service. Apparently proxy configs npm'not apply to node.js

Related questions

0 like 0 dislike
3 answers
0 like 0 dislike
3 answers
asked May 22, 2019 by strelkovandreyvalerievich
0 like 0 dislike
2 answers
0 like 0 dislike
1 answer
110,608 questions
257,187 answers
40,796 users