LukeBMM

Looking at the API response[1] implies a bit of formatting being done on the HN side. Maybe some of that is done before the limit.

The published version, with opening html paragraphs (except the first one, for some reason) and with html entities translated back into single characters, comes out to 1979 characters.

Your second link, formatted the same way, comes out to _exactly_ 2000 characters. The limit could potentially be strictly _less than_ 2000 characters. You may have been exactly one character off.

[1] https://hacker-news.firebaseio.com/v0/item/17388936.json?pri...

Just to expand a bit on what theomega was saying, the node_modules folder should generally be excluded from the repository.

The idea is that anyone can grab a copy and run npm install to get the devDependencies listed in package.json. Not only does that keep your repo cleaner but it also lets the package manager handle the management of packages.

The last part is the important bit. Anyone running npm install after Coveralls 3.0.1 came out, for example, would get the updated version and all the correspondingly updated dependencies. As it stands, anyone who grabs a copy of your repository and uses the included node_modules won't get all the non-breaking incremental updates to all the dev dependencies, their dependencies, etc.

Give me a few more years and I'll get back to you.

5 years experience: "What could possibly go wrong?"

10 years experience: "Here's a list of all the things I can think of that could go wrong."

15 years experience: "Here's the thing that could go wrong that matters to you."