Last 12 weeks · 0 commits
1 of 6 standards met
discount@0.2.3 preinstall /Users/mac/projects/depthray/website2/node_modules/.staging/discount-0e0ff4fe node-waf configure build sh: node-waf: command not found npm ERR! Darwin 15.5.0 npm ERR! argv "node" "/Users/mac/.meteor/packages/meteor-tool/.1.3.5_1.u6b5vm++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/bin/npm" "install" "--save" "discount" npm ERR! node v0.10.46 npm ERR! npm v3.10.5 npm ERR! file sh npm ERR! code ELIFECYCLE npm ERR! errno ENOENT npm ERR! syscall spawn npm ERR! discount@0.2.3 preinstall: npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the discount@0.2.3 preinstall script 'node-waf configure build'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the discount package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node-waf configure build npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs discount npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls discount npm ERR! There is likely additional logging output above. npm ERR! Please include the following file with any support request: npm ERR! /Users/mac/projects/depthray/website2/npm-debug.log
Repository: tj/node-discount. Description: nodejs bindings for the C markdown "discount" library Stars: 78, Forks: 7. Primary language: C++. Languages: C++ (69.6%), Python (19.4%), JavaScript (11.1%). Open PRs: 0, open issues: 10. Last activity: 13y ago. Community health: 28%. Top contributors: tj, RubenVerborgh, friggeri, aconbere, aklt, miksago, isaacs.
Here is a small fix that made node-discount build on my machine. Before this fix I was running into this error:
Hi TJ, I'm using your library for a small Express/CoffeeScript blog project, and I noticed that the output of would intermittently include extra characters on the end. To fix this, I dug through the source of RDiscount and found that writing the result of to a new buffer using the explicit length returned fixes the issue. In order to get the error to trigger, I had to increase the length of the test input and output docs and run the second test assertion in a for-loop. For some reason beyond me, the error only happens during the second iteration of the loop, and simply running the assertion twice doesn't cause it. Hope you find this useful, and thanks for all your hard work building the Node ecosystem, David Eisinger david.eisinger@gmail.com