A bot to automatically DCA (Dollar-Cost Average) buy cryptocurrency on Binance

Last update: Jan 6, 2023

Overview

Binance DCA (Dollar-Cost-Averaging) Bot

This bot allows you to sit back and relax while it automatically invests in cryptocurrency on the Binance exchange for you. The bot allows you to set up recurring buys for any cryptocurrency supported on the exchange at any interval you want. Both fiat to crypto and crypto to crypto purchases supported.

Getting Started

Create a Binance Account

Sign up to Binance if you do not already have an account and complete any verification that may be required. You can use my sign-up referral link here if you wish: https://www.binance.com/en/register?ref=W3V44WHT. By using this link you earn a small amount of BTC commission on any trades I make.

Generate API keys

Create a new API key on Binance. You should select Enable Reading and Enable Spot & Margin Trading for the restrictions.

Set up the project

Node.js v13 or higher required.

git clone https://github.com/lukeliasi/binance-dca-bot.git
cd binance-dca-bot
npm install

Configure the bot

Create a config.js file in the root, you can copy the example template: cp config.example.js config.js

Fill out each part of the config.js adding your Binance API keys and set up the buys.

Configuration Options:

Option	Description
`binance_key`	Your Binance API Key
`binance_secret`	Your Binance API Secret
`sendgrid_secret`	An optional SendGrid API key for the bot to send you email notifications when buy orders are executed
`notifications`	If using SendGrid notifications this value should be an object structured like so: `notifications: { to: "[email protected]", from: "[email protected]" }`
`buy`	Array of objects for each buy you want to set up.

Buy object:

Parameter	Description
`asset`	The asset you want to buy
`currency`	The currency you want to use to buy the asset. E.g: "USD", "GBP", "BTC" etc...
`quoteOrderQty` or `quantity`	Use `quoteOrderQty` for the amount you want to spend/invest or alternatively you can set `quantity` to buy a set amount of the asset regardless of price. Note Binance trading rules pairs have minimum and maximum order sizes
`schedule`	A cron expression to set when the buy order should execute for this asset. See Crontab.guru for help setting up schedules. You can omit this `schedule` parameter and the buy order will execute immediately

Start the bot

Use this command to start the bot: npm run start. The program must stay running, and it will execute the buy orders at the defined schedules using cron jobs.

Deployment

Consider running the bot in the cloud, so you do not need to run the bot constantly on your machine. I personally recommend and use a Vultr Cloud Compute VPS instance as the cheapest option. You can use my referal link here to receive $100 of credit for free: https://www.vultr.com/?ref=8768322-6G after you sign up.

You will want to use PM2 process manager or similar on the server which keeps the bot running and can restart the bot automatically if the server or program crashes.

Remember the remote server may be in a different timezone to you, run the command date to see the servers timezone to configure your cron accordingly.

Automating fiat deposits to Binance

For further automation you can deposit funds into your Binance account automatically via bank transfer. Simply initiate a fiat deposit (bank transfer) via the Binance website and note down the bank details you need to pay to. The reference code and other details never change, so you can set up a standing order with your bank to automatically transfer money to Binance on a schedule with these details.

As an exmaple, you could set up a standing order to deposit to Binance the day after you get paid, and then configure the bot to purchase your crypto the following day.

Donations

If you found this project helpful and would like to support me, you can donate to one of the following crypto addresses:

BTC: 1LeisHRv4yLyzQg6M79f48ej9cnkruh6WH
ETH: 0x804d2f31cc49a68011271b1d56884d0efa9e9ce9
DOGE: DBa2UFwonN4QcunXY8Thev9oCxMkDrr9rm
XRP: rEb8TK3gBgk5auZkwc6sHnwrGVJH8DuaLh tag: 101391719
USDT: 0x804d2f31cc49a68011271b1d56884d0efa9e9ce9

Disclaimer

Use at your own risk. I am not liable for how you use the bot.

License

MIT License

Comments

Added support to MongoDb Atlas + general improvements
Changelog

Added optional support to MongoDB Atlas to store performed orders results (for further analysis). Collection/Documents structure is as per New Order (TRADE) FULL Response Binance API documentation.

Made completely optional the config.js file (just needed to be there to simplify some logic, it can be removed with some additional work). Everything can now be fetched from Environment Variables (process.env.xxx), config.js file or a mix of the two.

Added more controls over config/env data in order to avoid unwanted behaviors.

Minor improvements.

PS: this is of course based on PR #9 and contains all those features.
opened by informagico 5

Unexpected reserved word

await runBot(); ^^^^^

SyntaxError: Unexpected reserved word

at Loader.moduleStrategy (internal/modules/esm/translators.js:88:18)
at async link (internal/modules/esm/module_job.js:41:21)

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node ./src/index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/linux/.npm/_logs/2021-09-01T00_38_33_541Z-debug.log

my log

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/home/linux/.nvm/versions/node/v14.4.0/bin/node',
1 verbose cli   '/home/linux/.nvm/versions/node/v14.4.0/bin/npm',
1 verbose cli   'run',
1 verbose cli   'start'
1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 info lifecycle [email protected]~start: [email protected]
7 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~start: PATH: /home/linux/.nvm/versions/node/v14.4.0/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/linux/binance-dca-bot/node_modules/.bin:/home/linux/.nvm/versions/node/v14.4.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle [email protected]~start: CWD: /home/linux/binance-dca-bot
10 silly lifecycle [email protected]~start: Args: [ '-c', 'node ./src/index.js' ]
11 silly lifecycle [email protected]~start: Returned: code: 1  signal: null
12 info lifecycle [email protected]~start: Failed to exec start script
13 verbose stack Error: [email protected] start: `node ./src/index.js`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/home/linux/.nvm/versions/node/v14.4.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:315:20)
13 verbose stack     at ChildProcess.<anonymous> (/home/linux/.nvm/versions/node/v14.4.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:315:20)
13 verbose stack     at maybeClose (internal/child_process.js:1051:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
14 verbose pkgid [email protected]
15 verbose cwd /home/linux/binance-dca-bot
16 verbose Linux 5.11.0-27-generic
17 verbose argv "/home/linux/.nvm/versions/node/v14.4.0/bin/node" "/home/linux/.nvm/versions/node/v14.4.0/bin/npm" "run" "start"
18 verbose node v14.4.0
19 verbose npm  v6.14.5
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] start: `node ./src/index.js`
22 error Exit status 1
23 error Failed at the [email protected] start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Could you help me ? Thanks

duplicate

opened by cryptonobo 4

Cron / schedule paramter issue in trade.js

Hello. So I am trying to set this up and I am running into the following issue and I can no see anything wrong with my cron pattern. It is valid according to crontab.guru. I want to execute a buy at 16:00 (or 4:00pm) every wednesday but the bot seems to not know how to handle the number 16. What am I doing wrong?

Please also see the attached screenshot.

opened by WinMinerGMX 3
Unexpected reserved word in 'await' runBot() in index.js

Hi! I was trying to deploy this bot on a Vultr Ubuntu 21.04 VPS but got the following error when executing sudo npm run start.

However, I tried running the bot on a Windows 10 system and it seemed to work fine but I really wanted to test this out on a Ubuntu VPS.

My index.js file is as presented in the repo.

Terminal output:

lcvalves@vultr:~/binance-dca-bot$ npm run start `> [email protected] start` `> node ./src/index.js` file:///home/lcvalves/binance-dca-bot/src/index.js:59 await runBot(); ^^^^^

SyntaxError: Unexpected reserved word at Loader.moduleStrategy (internal/modules/esm/translators.js:133:18) at async link (internal/modules/esm/module_job.js:42:21) npm ERR! code 1 npm ERR! path /home/lcvalves/binance-dca-bot npm ERR! command failed npm ERR! command sh -c node ./src/index.js

npm ERR! A complete log of this run can be found in: npm ERR! /home/lcvalves/.npm/_logs/2021-05-23T21_13_07_258Z-debug.log

Log:

0 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'start' ] 1 info using [email protected] 2 info using [email protected] 3 timing config:load:defaults Completed in 1ms 4 timing config:load:file:/usr/share/nodejs/npm/npmrc Completed in 2ms 5 timing config:load:builtin Completed in 2ms 6 timing config:load:cli Completed in 1ms 7 timing config:load:env Completed in 1ms 8 timing config:load:file:/home/lcvalves/binance-dca-bot/.npmrc Completed in 0ms 9 timing config:load:project Completed in 1ms 10 timing config:load:file:/home/lcvalves/.npmrc Completed in 0ms 11 timing config:load:user Completed in 0ms 12 timing config:load:file:/etc/npmrc Completed in 0ms 13 timing config:load:global Completed in 0ms 14 timing config:load:cafile Completed in 0ms 15 timing config:load:validate Completed in 1ms 16 timing config:load:setUserAgent Completed in 0ms 17 timing config:load:setEnvs Completed in 1ms 18 timing config:load Completed in 9ms 19 verbose npm-session 2578695e0cfbb54c 20 timing npm:load Completed in 19ms 21 timing command:run-script Completed in 115ms 22 verbose stack Error: command failed 22 verbose stack at ChildProcess.<anonymous> (/usr/share/nodejs/@npmcli/promise-spawn/index.js:64:27) 22 verbose stack at ChildProcess.emit (events.js:314:20) 22 verbose stack at maybeClose (internal/child_process.js:1022:16) 22 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5) 23 verbose pkgid [email protected] 24 verbose cwd /home/lcvalves/binance-dca-bot 25 verbose Linux 5.11.0-16-generic 26 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "start" 27 verbose node v12.21.0 28 verbose npm v7.5.2 29 error code 1 30 error path /home/lcvalves/binance-dca-bot 31 error command failed 32 error command sh -c node ./src/index.js 33 verbose exit 1

Any clues on how to fix this?

opened by lcvalves 2

error: unexpected reserved word

I am getting a error when trying to run on windows.

C:\binance-dca-bot-main>npm run start

> [email protected] start C:\binance-dca-bot-main
> node ./src/index.js

(node:18324) ExperimentalWarning: The ESM module loader is experimental.
file:///C:/binance-dca-bot-main/src/index.js:59
await runBot();
^^^^^

SyntaxError: Unexpected reserved word
    at Loader.moduleStrategy (internal/modules/esm/translators.js:88:18)
    at async link (internal/modules/esm/module_job.js:41:21)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node ./src/index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\AppData\Roaming\npm-cache\_logs\2021-05-21T08_46_23_456Z-debug.log

C:\binance-dca-bot-main>

opened by KeyboardDabbler 2

Bump node-fetch from 2.6.1 to 3.1.1
Bumps node-fetch from 2.6.1 to 3.1.1.

Release notes

Sourced from node-fetch's releases.

v3.1.1

Security patch release

Recommended to upgrade, to not leak sensitive cookie and authentication header information to 3th party host while a redirect occurred

What's Changed

core: update fetch-blob by @jimmywarting in node-fetch/node-fetch#1371

docs: Fix typo around sending a file by @jimmywarting in node-fetch/node-fetch#1381

core: (http.request): Cast URL to string before sending it to NodeJS core by @jimmywarting in node-fetch/node-fetch#1378

core: handle errors from the request body stream by @mdmitry01 in node-fetch/node-fetch#1392

core: Better handle wrong redirect header in a response by @tasinet in node-fetch/node-fetch#1387

core: Don't use buffer to make a blob by @jimmywarting in node-fetch/node-fetch#1402

docs: update readme for TS @types/node-fetch by @adamellsworth in node-fetch/node-fetch#1405

core: Fix logical operator priority to disallow GET/HEAD with non-empty body by @maxshirshin in node-fetch/node-fetch#1369

core: Don't use global buffer by @jimmywarting in node-fetch/node-fetch#1422

ci: fix main branch by @dnalborczyk in node-fetch/node-fetch#1429

core: use more node: protocol imports by @dnalborczyk in node-fetch/node-fetch#1428

core: Warn when using data by @jimmywarting in node-fetch/node-fetch#1421

docs: Create SECURITY.md by @JamieSlome in node-fetch/node-fetch#1445

core: don't forward secure headers to 3th party by @jimmywarting in node-fetch/node-fetch#1449

New Contributors

@mdmitry01 made their first contribution in node-fetch/node-fetch#1392

@tasinet made their first contribution in node-fetch/node-fetch#1387

@adamellsworth made their first contribution in node-fetch/node-fetch#1405

@maxshirshin made their first contribution in node-fetch/node-fetch#1369

@JamieSlome made their first contribution in node-fetch/node-fetch#1445

Full Changelog: https://github.com/node-fetch/node-fetch/compare/v3.1.0...v3.1.1

v3.1.0

What's Changed

fix(Body): Discourage form-data and buffer() by @jimmywarting in node-fetch/node-fetch#1212

fix: Pass url string to http.request by @serverwentdown in node-fetch/node-fetch#1268

Fix octocat image link by @lakuapik in node-fetch/node-fetch#1281

fix(Body.body): Normalize Body.body into a node:stream by @jimmywarting in node-fetch/node-fetch#924

docs(Headers): Add default Host request header to README.md file by @robertoaceves in node-fetch/node-fetch#1316

Update CHANGELOG.md by @jimmywarting in node-fetch/node-fetch#1292

Add highWaterMark to cloned properties by @davesidious in node-fetch/node-fetch#1162

Update README.md to fix HTTPResponseError by @thedanfernandez in node-fetch/node-fetch#1135

docs: switch url to URL by @dhritzkiv in node-fetch/node-fetch#1318

fix(types): declare buffer() deprecated by @dnalborczyk in node-fetch/node-fetch#1345

chore: fix lint by @dnalborczyk in node-fetch/node-fetch#1348

refactor: use node: prefix for imports by @dnalborczyk in node-fetch/node-fetch#1346

Bump data-uri-to-buffer from 3.0.1 to 4.0.0 by @dependabot in node-fetch/node-fetch#1319

Bump mocha from 8.4.0 to 9.1.3 by @dependabot in node-fetch/node-fetch#1339

Referrer and Referrer Policy by @tekwiz in node-fetch/node-fetch#1057

Add typing for Response.redirect(url, status) by @c-w in node-fetch/node-fetch#1169

chore: Correct stuff in README.md by @Jiralite in node-fetch/node-fetch#1361

docs: Improve clarity of "Loading and configuring" by @serverwentdown in node-fetch/node-fetch#1323

feat(Body): Added support for BodyMixin.formData() and constructing bodies with FormData by @jimmywarting in node-fetch/node-fetch#1314

... (truncated)

Changelog

Sourced from node-fetch's changelog.

Changelog

All notable changes will be recorded here.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

What's Changed

core: update fetch-blob by @jimmywarting in node-fetch/node-fetch#1371

docs: Fix typo around sending a file by @jimmywarting in node-fetch/node-fetch#1381

core: (http.request): Cast URL to string before sending it to NodeJS core by @jimmywarting in node-fetch/node-fetch#1378

core: handle errors from the request body stream by @mdmitry01 in node-fetch/node-fetch#1392

core: Better handle wrong redirect header in a response by @tasinet in node-fetch/node-fetch#1387

core: Don't use buffer to make a blob by @jimmywarting in node-fetch/node-fetch#1402

docs: update readme for TS @types/node-fetch by @adamellsworth in node-fetch/node-fetch#1405

core: Fix logical operator priority to disallow GET/HEAD with non-empty body by @maxshirshin in node-fetch/node-fetch#1369

core: Don't use global buffer by @jimmywarting in node-fetch/node-fetch#1422

ci: fix main branch by @dnalborczyk in node-fetch/node-fetch#1429

core: use more node: protocol imports by @dnalborczyk in node-fetch/node-fetch#1428

core: Warn when using data by @jimmywarting in node-fetch/node-fetch#1421

docs: Create SECURITY.md by @JamieSlome in node-fetch/node-fetch#1445

core: don't forward secure headers to 3th party by @jimmywarting in node-fetch/node-fetch#1449

New Contributors

@mdmitry01 made their first contribution in node-fetch/node-fetch#1392

@tasinet made their first contribution in node-fetch/node-fetch#1387

@adamellsworth made their first contribution in node-fetch/node-fetch#1405

@maxshirshin made their first contribution in node-fetch/node-fetch#1369

@JamieSlome made their first contribution in node-fetch/node-fetch#1445

Full Changelog: https://github.com/node-fetch/node-fetch/compare/v3.1.0...v3.1.2

3.1.0

What's Changed

fix(Body): Discourage form-data and buffer() by @jimmywarting in node-fetch/node-fetch#1212

fix: Pass url string to http.request by @serverwentdown in node-fetch/node-fetch#1268

Fix octocat image link by @lakuapik in node-fetch/node-fetch#1281

fix(Body.body): Normalize Body.body into a node:stream by @jimmywarting in node-fetch/node-fetch#924

docs(Headers): Add default Host request header to README.md file by @robertoaceves in node-fetch/node-fetch#1316

Update CHANGELOG.md by @jimmywarting in node-fetch/node-fetch#1292

Add highWaterMark to cloned properties by @davesidious in node-fetch/node-fetch#1162

Update README.md to fix HTTPResponseError by @thedanfernandez in node-fetch/node-fetch#1135

docs: switch url to URL by @dhritzkiv in node-fetch/node-fetch#1318

fix(types): declare buffer() deprecated by @dnalborczyk in node-fetch/node-fetch#1345

chore: fix lint by @dnalborczyk in node-fetch/node-fetch#1348

refactor: use node: prefix for imports by @dnalborczyk in node-fetch/node-fetch#1346

Bump data-uri-to-buffer from 3.0.1 to 4.0.0 by @dependabot in node-fetch/node-fetch#1319

Bump mocha from 8.4.0 to 9.1.3 by @dependabot in node-fetch/node-fetch#1339

Referrer and Referrer Policy by @tekwiz in node-fetch/node-fetch#1057

Add typing for Response.redirect(url, status) by @c-w in node-fetch/node-fetch#1169

... (truncated)

Commits

36e47e8 3.1.1 release (#1451)

5304f3f Don't change relative location header on manual redirect (#1105)

f5d3cf5 fix(Headers): don't forward secure headers to 3th party (#1449)

f2c3d56 Create SECURITY.md (#1445)

4ae3538 core: Warn when using data (#1421)

41f53b9 fix: use more node: protocol imports (#1428)

f674875 ci: fix main branch (#1429)

1493d04 core: Don't use global buffer (#1422)

eb33090 Chore: Fix logical operator priority (regression) to disallow GET/HEAD with n...

7ba5bc9 update readme for TS @type/node-fetch (#1405)

Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by endless, a new releaser for node-fetch since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 1
Issue defining multiple assets in trades.js

Hello again. I am facing another issue that I am unable to solve on my own. I defined multiple assets for buying in trade.js however I am getting a syntax error again and I can't figure out where my snytax is wrong. I tried to follow how trades are defined in the .env file with { and } encapsulating every asset, but I get the error below. I tried without { and } and with a singe { and } encapsulating the entire list of 5 assets but nothing works.

It looks like the bot is taking issue with the { in line 14, the second asset, and I do not know why.

See screenshot below.

Can you help me one more time?

opened by WinMinerGMX 1
Getting the following error after npm run start

import { BinanceAPI } from "./services/binance-api.js"; ^

SyntaxError: Unexpected token { at Module._compile (internal/modules/cjs/loader.js:723:23) at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) at Module.load (internal/modules/cjs/loader.js:653:32) at tryModuleLoad (internal/modules/cjs/loader.js:593:12) at Function.Module._load (internal/modules/cjs/loader.js:585:3) at Function.Module.runMain (internal/modules/cjs/loader.js:831:12) at startup (internal/bootstrap/node.js:283:19) at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] start: node ./src/index.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

opened by careonecomm 1
Updated to v2.0.0

This is based on PR #9 and PR #10 with major (breaking) changes over the main branch.

Changelog over #9 and #10

Dropped support to config.js in favor of .env/Environment Variables and trades.js. Added support to .env file. Updated README.md with all the new settings. Minor improvements on bot methods.

opened by informagico 0
feat: add Docker image

Thanks for this cool project! Dropping here my small proposal: this is a very simple Dockerfile for those that might like using Docker to execute this bot (for instance: no need to install NodeJs).

opened by fllaca 0
Bump axios from 0.21.1 to 0.21.4
Bumps axios from 0.21.1 to 0.21.4.

Release notes

Sourced from axios's releases.

v0.21.4

0.21.4 (September 6, 2021)

Fixes and Functionality:

Fixing JSON transform when data is stringified. Providing backward compatibility and complying to the JSON RFC standard (#4020)

Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub:

Guillaume Fortaine

Yusuke Kawasaki

Dmitriy Mozgovoy

v0.21.3

0.21.3 (September 4, 2021)

Fixes and Functionality:

Fixing response interceptor not being called when request interceptor is attached (#4013)

Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub:

Julian Hollmann

v0.21.2

0.21.2 (September 4, 2021)

Fixes and Functionality:

Updating axios requests to be delayed by pre-emptive promise creation (#2702)

Adding "synchronous" and "runWhen" options to interceptors api (#2702)

Updating of transformResponse (#3377)

Adding ability to omit User-Agent header (#3703)

Adding multiple JSON improvements (#3688, #3763)

Fixing quadratic runtime and extra memory usage when setting a maxContentLength (#3738)

Adding parseInt to config.timeout (#3781)

Adding custom return type support to interceptor (#3783)

Adding security fix for ReDoS vulnerability (#3980)

Internal and Tests:

Updating build dev dependancies (#3401)

Fixing builds running on Travis CI (#3538)

Updating follow rediect version (#3694, #3771)

Updating karma sauce launcher to fix failing sauce tests (#3712, #3717)

Updating content-type header for application/json to not contain charset field, according do RFC 8259 (#2154)

Fixing tests by bumping karma-sauce-launcher version (#3813)

Changing testing process from Travis CI to GitHub Actions (#3938)

Documentation:

Updating documentation around the use of AUTH_TOKEN with multiple domain endpoints (#3539)

... (truncated)

Changelog

Sourced from axios's changelog.

0.21.4 (September 6, 2021)

Fixes and Functionality:

Fixing JSON transform when data is stringified. Providing backward compatability and complying to the JSON RFC standard (#4020)

Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub:

Jay

Guillaume Fortaine

Yusuke Kawasaki

Dmitriy Mozgovoy

0.21.3 (September 4, 2021)

Fixes and Functionality:

Fixing response interceptor not being called when request interceptor is attached (#4013)

Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub:

Jay

Julian Hollmann

0.21.2 (September 4, 2021)

Fixes and Functionality:

Updating axios requests to be delayed by pre-emptive promise creation (#2702)

Adding "synchronous" and "runWhen" options to interceptors api (#2702)

Updating of transformResponse (#3377)

Adding ability to omit User-Agent header (#3703)

Adding multiple JSON improvements (#3688, #3763)

Fixing quadratic runtime and extra memory usage when setting a maxContentLength (#3738)

Adding parseInt to config.timeout (#3781)

Adding custom return type support to interceptor (#3783)

Adding security fix for ReDoS vulnerability (#3980)

Internal and Tests:

Updating build dev dependancies (#3401)

Fixing builds running on Travis CI (#3538)

Updating follow rediect version (#3694, #3771)

Updating karma sauce launcher to fix failing sauce tests (#3712, #3717)

Updating content-type header for application/json to not contain charset field, according do RFC 8259 (#2154)

Fixing tests by bumping karma-sauce-launcher version (#3813)

Changing testing process from Travis CI to GitHub Actions (#3938)

Documentation:

Updating documentation around the use of AUTH_TOKEN with multiple domain endpoints (#3539)

Remove duplication of item in changelog (#3523)

... (truncated)

Commits

66c4602 Merge branch 'master' into release/0.21.4

fc15665 [Releasing] v0.21.4

c2714f0 [Updating] incorrect JSON syntax in README.md

0fc7248 fix json transform when data is pre-stringified (#4020)

90205f8 Change headers type to string record (#3021)

92b29d2 Make the default type of response data never (#3002)

4eeb3b1 Improved type-safety for AxiosRequestConfig (#2995)

cd7ff04 Adding HTTP status code to error.toJSON (#2956)

b5a1a67 Adding nodejs http.request option: insecureHTTPParser (#2930)

4f25380 Exposing the Axios constructor in index.d.ts (#2872)

Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by jasonsaayman, a new releaser for axios since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 0
Bump node-fetch from 2.6.1 to 2.6.7
Bumps node-fetch from 2.6.1 to 2.6.7.

Release notes

Sourced from node-fetch's releases.

v2.6.7

Security patch release

Recommended to upgrade, to not leak sensitive cookie and authentication header information to 3th party host while a redirect occurred

What's Changed

fix: don't forward secure headers to 3th party by @jimmywarting in node-fetch/node-fetch#1453

Full Changelog: https://github.com/node-fetch/node-fetch/compare/v2.6.6...v2.6.7

v2.6.6

What's Changed

fix(URL): prefer built in URL version when available and fallback to whatwg by @jimmywarting in node-fetch/node-fetch#1352

Full Changelog: https://github.com/node-fetch/node-fetch/compare/v2.6.5...v2.6.6

v2.6.2

fixed main path in package.json

Commits

1ef4b56 backport of #1449 (#1453)

8fe5c4e 2.x: Specify encoding as an optional peer dependency in package.json (#1310)

f56b0c6 fix(URL): prefer built in URL version when available and fallback to whatwg (...

b5417ae fix: import whatwg-url in a way compatible with ESM Node (#1303)

18193c5 fix v2.6.3 that did not sending query params (#1301)

ace7536 fix: properly encode url with unicode characters (#1291)

152214c Fix(package.json): Corrected main file path in package.json (#1274)

See full diff in compare view

Maintainer changes

This version was pushed to npm by endless, a new releaser for node-fetch since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 0
Replace the legacy querystring API by the URLSearchParams API

The querystring API is considered Legacy. While it is still maintained, new code should use the API instead. (query-string is a package and URLSearchParams is a native interface.)

opened by Eddict 0
API key does not start with "SG.".

Hello dear developer team, Please help me in resolving the following error:

npm run start

[email protected] start /home/beisserikbay/binance-dca-bot node src/bot.js API key does not start with "SG.". /home/beisserikbay/binance-dca-bot/node_modules/mongodb-connection-string-url/lib/index.js:66 throw new MongoParseError(Invalid connection string "${uri}"); ^ MongoParseError: Invalid connection string "your-mongodb-atlas-uri" at new ConnectionString (/home/beisserikbay/binance-dca-bot/node_modules/mongodb-connection-string-url/lib/inde x.js:66:19) at Object.parseOptions (/home/beisserikbay/binance-dca-bot/node_modules/mongodb/lib/connection_string.js:210:17 ) at new MongoClient (/home/beisserikbay/binance-dca-bot/node_modules/mongodb/lib/mongo_client.js:62:46) at new MongoDb (file:///home/beisserikbay/binance-dca-bot/src/services/mongodb.js:14:17) at file:///home/beisserikbay/binance-dca-bot/src/bot.js:57:17 at ModuleJob.run (internal/modules/esm/module_job.js:183:25) at async Loader.import (internal/modules/esm/loader.js:178:24) at async Object.loadESM (internal/process/esm_loader.js:68:5) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] start: node src/bot.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/beisserikbay/.npm/_logs/2021-12-16T21_58_30_042Z-debug.log

opened by kafarik 1