CCXT Pro Websockets merged with CCXT!

[kroitor]

Dear users of CCXT and CCXT Pro!

We are happy to announce the merge of CCXT Pro into CCXT.
CCXT Pro is now a part of the free CCXT package as of version 1.95+
All of the CCXT Pro Websocket functionality is retained in CCXT.
Please, make sure to upgrade your scripts accordingly.
You can find the examples here:

• https://github.com/ccxt/ccxt/tree/master/examples/
• https://github.com/ccxt/ccxt/tree/master/examples/ccxt.pro

CCXT Wiki: https://github.com/ccxt/ccxt/wiki/
CCXT Manual: https://github.com/ccxt/ccxt/wiki/Manual
CCXT Pro Manual: https://github.com/ccxt/ccxt/wiki/ccxt.pro.manual

All feedback is very welcome and is especially valued during this period of transition.

A word to existing CCXT Pro users: please, ignore the subscription expiry notifications and switch to CCXT. Don't hesitate to reach out to us here on GitHub and in Discord (https://discord.gg/ccxt) in case you have any difficulties migrating or if you have any questions regarding the merge.

Thanks for using CCXT!

Yours faithfully,
The CCXT Dev Team.

[jshcrowthe]

First of all thanks to all on the hard work here! As a user, the added OSS functionality is much appreciated.

I noticed that the API surface has now changed. Whereas before the import scheme was:

import * as ccxt from ccxt;

// Do CCXT things

Importing CCXT as originally documented the watch functionality is not available. Instead I have to import at the pro subpath:

ESM

import { pro as ccxt } from ccxt;

// Do CCXT things

CommonJS

const ccxt = require('ccxt').pro;

// Do CCXT things

Is the plan here to merge both API interfaces into one? Or is the "pro" entrypoint going to be an ongoing thing?

[frosty00]

@jshcrowthe we're going to add esm support soon #12619

[xiguakaoya]

thx!

[ambrosestartup]

Thank you!

[jshcrowthe]

@frosty00 I mean less about strict ESM support (as you can emulate that w/ any modern build system these days) and more the specifics of having to explicitly reference require('ccxt').pro in order to get the watch behavior.

Is the plan to make it so someone doing const ccxt = require('ccxt') gets the watch behavior (and therefore requires the consolidation of the implementations for ccxt and ccxt.pro, or are y'all wanting to keep them separate?

i.e. should the following snippet work?

const ccxt = require('ccxt');

async function main() {
  const exchange = new ccxt.ftx();
  const book = await exchange.watchOrderBook();
  console.log(book);
}

main();

And if not, what's the rationale?

[suenot]

Игорь, спасибо тебе!

[suenot]

Simple example:

const ccxt = require ('ccxt').pro;

(async () => {

  const exchange = new ccxt.binance({ enableRateLimit: true })

  while (true) {
    const orderbook = await exchange.watchOrderBook('ETH/BTC')
    console.log (new Date (), orderbook['asks'][0], orderbook['bids'][0])
  }

}) ()