npm run build on Windows
See original GitHub issueI’m getting errors on Windows 10 when trying to npm run build
and node run-tests
.
From npm run build
in update-badges
:
> ccxt@1.9.326 update-badges C:\Users\kinga\Documents\GitHub\ccxt
> node update-badges
Preparing for PyPI → ./python/README.rst (pipez.js:23)
C:\Users\kinga\Documents\GitHub\ccxt\update-badges.js:24
let rstExchangeTableLines = match[2].split ("\n")
^
TypeError: Cannot read property '2' of null
at Object.<anonymous> (C:\Users\kinga\Documents\GitHub\ccxt\update-badges.js:24:34)
at Module._compile (module.js:624:30)
at Object.Module._extensions..js (module.js:635:10)
at Module.load (module.js:545:32)
at tryModuleLoad (module.js:508:12)
at Function.Module._load (module.js:500:3)
at Function.Module.runMain (module.js:665:10)
at startup (bootstrap_node.js:187:16)
at bootstrap_node.js:608:3
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! ccxt@1.9.326 update-badges: `node update-badges`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ccxt@1.9.326 update-badges 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:\Users\kinga\AppData\Roaming\npm-cache\_logs\2017-11-01T20_53_13_376Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! ccxt@1.9.326 build: `npm run export-exchanges && npm run vss && npm run pandoc-python-readme && npm run pandoc-doc-readme && npm run pandoc-doc-manual && npm run pandoc-doc-install && npm run pandoc-doc-exchanges && npm run pandoc-doc-exchanges-by-country && npm run transpile && npm run update-badges && npm run browserify`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ccxt@1.9.326 build 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:\Users\kinga\AppData\Roaming\npm-cache\_logs\2017-11-01T20_53_13_452Z-debug.log
From node run-tests
:
C:\Users\kinga\Documents\GitHub\ccxt>node run-tests
Testing { exchanges: <array[90]>, symbol: "all", keys: { '--js': false, '--php': false, '--python': false, '--python3': false } } (pipez.js:23)
[Error] spawn python2 ENOENT
at _errnoException util.js:1021
at onexit internal/child_process.js:192
at onErrorNT internal/child_process.js:374
at _combinedTickCallback internal/process/next_tick.js:138
at _tickCallback internal/process/next_tick.js:180 (pipez.js:23)
Issue Analytics
- State:
- Created 6 years ago
- Comments:35 (32 by maintainers)
Top Results From Across the Web
NPM run build not working in Windows specific directory
install Git; go to project folder and right click to access context menu; from there run Git bash here; run the command: npm...
Read more >npm-build
This is the plumbing command called by npm link and npm install . It should generally be called during installation, but if you...
Read more >Use Azure Pipelines to build and publish a Node.js package
An Azure DevOps organization and project. Create one for free. An ability to run pipelines on Microsoft-hosted agents. You can either purchase a ......
Read more >Problem with npm run build - Questions - n8n community
npm install -g node-gyp npm i python npm install --global --production windows-build-tools npm config set python “D:\Python27\python.exe”
Read more >'npm run build' doesn't create Archive.zip
operable program or batch file.) I have tried downloading winzip and 7zip, I have copied both to my windows environment variable, but i...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You should not run
run-tests --js node
you should runnode run-tests --js
)) I guess, it’s just a typo.As for the cause: when all of them are failing, there’s most likely some simple reason, like a missing module or something. Try running a test for one exchange to see the detailed cause of the failure:
↑ That should show the cause of failures. After fixing it, the other failures should go away as well, and the
node run-tests --js
should pass. Let us know if it does not help.Hi kroitor,
I have fix problems, error ‘cp’ i installed cygwin to compile on windown. Everything seems very good when running ‘npm run build’ does not generate errors. But when running ‘run-tests --js node’, bad things happen. it fails.
Thanks kroitor! ---------------------- image capture bug ------------------------------