Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Expecting a finite number

See original GitHub issue

Given example

const cryptoRandomString = require('crypto-random-string');
cryptoRandomString({length: 10});

throws TypeError: expecting a finite number

Issue Analytics

State:
Created 4 years ago
Comments:7 (2 by maintainers)

Top GitHub Comments

9reactions

philippboschcommented, Jan 3, 2021

I ran into the exact same problem and figured out what happened. Maybe this helps others.

Before I found this package, I initially installed the unique-string package which has a dependency on "crypto-random-string": "^2.0.0". When installing crypto-random-string npm apparently just used the already installed version instead of the latest available. So I ended up with version 2.0.0 for which the function signature is different, i.e. instead of something like { length: 10 } it expects just the length as an integer as the first argument. So when you pass it an object, it will fail with TypeError: Expected a finite number.

I fixed it by uninstalling both packages and re-instaling crypto-random-string. This gave me version 3.3.0.

0reactions

Edddo123commented, Mar 31, 2021

The answer @philippbosch wrote is correct. The problem is in versioning. The easier solution would be just to install this module at specific version. npm install crypto-random-string@3.3.1