Jeffrey Wear

No, that should not be happening. How do you know that is happening?

> Disabling NPM shell scripts fails to start my nodejs app. I get a package.json not found error. Hm I would figure that you should have a `package.json` file prior...

Ok I deleted my previous comment talking about trial-and-error since I found [the spec](https://unicode.org/reports/tr51/#Diversity). In particular, it says: > an emoji modifier must immediately follow [the] base emoji character and...

The Gist linked from my previous comment doesn't support applying different modifiers to each person in a [multi-person grouping](https://unicode.org/reports/tr51/#Multi_Person_Groupings). I'm currently adding support for that and will probably publish the...

Two more gotchas I've found: Firstly, the [basic algorithm](https://gist.github.com/wearhere/97528e81da82387d5fa4aa788856cdc1#file-playground-swift-L39) may return results that won't actually render in cases where platforms haven't generally added support for rendering all the different variants....

I am curious though, why? This is a severe gotcha when using `request` and `express`, since by default `request` uses `qs` to serialize querystrings using the indices format, and `express`...

Oh, it would make sense to me if the array were truncated at some point. But isn't the array completely parsed at present? It just happens to be completely parsed...

> I believe this is to prevent someone sending foo[999999999999]: LOL Ahh, as opposed to, I had been thinking, `foo[0]=LOL&foo[1]=LOL&…foo[999999999999]=LOL`. > having everything be objects instead of arrays would be...

That's a good stopgap. `express` doesn't expose configuration for its querystring parsing, but asking them to do so is a reasonable request. (EDIT: see bottom.) To make parsing unambiguous, I...

> I see the argument for making `arrayLimit` default to zero - it means there's no "magic number" at which param parsing changes, and anyone who wants the behavior can...