npm run build
...
> ccxt@1.18.361 update-badges /Users/nickpomfret/projects/ccxt.fork
> node build/update-badges
Preparing for PyPI → ./python/README.rst (<anonymous> @ update-badges.js:18)
/Users/nickpomfret/projects/ccxt.fork/build/update-badges.js:30
let rstExchangeTableLines = match[2].split ("\n")
^
TypeError: Cannot read property '2' of null
at Object.<anonymous> (<...>/ccxt/build/update-badges.js:30:34)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Function.Module.runMain (module.js:694:10)
at startup (bootstrap_node.js:204:16)
at bootstrap_node.js:625:3
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! ccxt@1.18.361 update-badges: `node build/update-badges`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ccxt@1.18.361 update-badges script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
- OS: os x
- Programming Language version: node 8.14.0
- CCXT version: “1.18.361”
I have pulled from upstream master and rebuilded docker image
Same problem here despite using docker.
npm run build-without-docsbuilds without errors.@o3o3o thx for the followup! We will switch to md
long_description_formatfor the python package in the coming days, so the README.rst will be excluded from the build.@npomfret Sorry for not responding for too long. Just curious — did you figure how to solve the issue?
We suggest to use Docker for building/testing/developing CCXT, to avoid the need of installing all the dependencies to your dev machine — which can be really troublesome in some cases.
If you’re using OSX it is easy:
cdto it, then rundocker-compose run --rm ccxtAfter some minutes of downloading and building the dependencies, you will get into the bash shell where you can run CCXT’s build scripts without a problem.
The filesystem inside of that container will be mapped to the original repo’s folder. So you can perfectly use it for developing your own fork!