Update npm to latest version

[mrlannigan]

Published version with npm is at 0.6.0 which is based on 41a9b5e.

This commit is before f93e0ee, which contains a fix for the facet pivot addition.

Can we get an updated version to npm?

[nicolasembleton]

Yes. Good point. Will do now I have some more time.

[luketaverne]

Also going to start working on this package again.

[mrlannigan]

@luketaverne this would be amazing. Thanks! If you guys need help let me know.

[sudowork]

@nicolasembleton Would also appreciate a new version being published. Was excited for the feature in 0.6.0 to allow POST requests for large requests; however, I noticed that the query params were being included in both the body and the URI still, causing 414 errors. Seems like 2a57e78 fixes the issue, but hasn't been published yet. Thanks!

[nicolasembleton]

Yes this one is very long overdue... Thanks for the reminder. Will try to
push it over the weekend.

On Thu, Oct 13, 2016 at 3:24 AM Kevin Gao notifications@github.com wrote:

@nicolasembleton https://github.com/nicolasembleton Would also
appreciate a new version being published. Was excited for the feature in
0.6.0 to allow POST requests for large requests; however, I noticed that
the query params were being included in both the body and the URI still,
causing 414 errors. Seems like 2a57e78
2a57e78
fixes the issue, but hasn't been published yet. Thanks!

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
#189 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABeXpFt2c2YJ9_ca5eGgp_ZwAVrl3D4Hks5qzUHzgaJpZM4JMvSm
.

[sudowork]

Awesome, really appreciate it! Have a great one.

[smashercosmo]

@nicolasembleton any luck with cutting new release?)) I'm mostly interested in #172 This is very critical bug fix. Would be glad to provide any help if needed.

[smashercosmo]

@nicolasembleton @lbdremy any response on this?

[nicolasembleton]

I'll make it done by this weekend! Can't delay that any longer.

…

On Wed, Nov 30, 2016 at 4:10 PM smashercosmo ***@***.***> wrote: @nicolasembleton <https://github.com/nicolasembleton> @lbdremy <https://github.com/lbdremy> any response on this? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#189 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABeXpB1dFnCoMHijKI1n2Hf0BoOitlnmks5rDT2DgaJpZM4JMvSm> .

[nicolasembleton]

@smashercosmo Would you mind making tests pointing your NPM directly to this commit: dcf31c2 ? Just to make sure everything works fine.

[nicolasembleton]

Release note, let me know guys if I have missed anything:

- `*` escaping fl parameter in Query (@Grzegorz Wilk)
- feat(Error): Properly capture and proxy status codes and error messages (@jsvk)
- Do not send the parameters in the url when using POST. (@voidberg)
- Add support for ipv6 when resolving host/hostname (@fractalf)
- URI encode the cursorMark value before use (@flawless2011)
- Only check options.pivot.mincount if options.pivot is available. (@saschagoebel)
- test(rangeFilter): test array of multiple fields and obj of single field (@luketaverne)

[smashercosmo]

@nicolasembleton awesome, thx. I'll test on wednesday.

[lebolo]

@nicolasembleton @luketaverne any chance of publishing the latest code to npm? Particularly interested in the pivot fix.

[nicolasembleton]

Hi Luis, Would you mind testing the latest commit? It's ready to push but need someone to do double testing before I can push. If it works fine, I'll push it over the weekend. Thanks, Nicolas.

…

On Thu, Dec 22, 2016 at 12:22 AM Luis Lebolo ***@***.***> wrote: @nicolasembleton <https://github.com/nicolasembleton> @luketaverne <https://github.com/luketaverne> any chance of publishing the latest code to npm? Particularly interested in the pivot fix. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#189 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABeXpOZPxVBpYCtc5XfxceG2EvJV7-Mvks5rKWA2gaJpZM4JMvSm> .

[sudowork]

@nicolasembleton, Any luck on getting the next version published?

[ghost]

Would be great to get another release to address https://nodesecurity.io/advisories/309 in the latest merge to master.

[nicolasembleton]

Excellent point. Very important one... I should have time next week to push a new version including the latest PRs.

…

On Sat, Apr 22, 2017 at 4:15 AM ministrycrm ***@***.***> wrote: Would be great to get another release to address https://nodesecurity.io/advisories/309 in the latest merge to master. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#189 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABeXpJTgVWICRbazFmQILFamVZqeO53Qks5ryRyOgaJpZM4JMvSm> .