
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
@httpie/collections
Advanced tools
async/await-ready array methods for Node.js
Installation · Docs · Usage
Follow @marcuspoehls and @httpiejs for updates!
The @httpie/collections package provides a convenient wrapper to work with arrays.
npm i @httpie/collections
Find all the details and available methods in the extensive Supercharge docs.
The package exports a function accepting an array as a parameter. From there, you can chain all collection methods.
A created collection (Collect([1, 2, 3])) is synchronous by default. That means it behaves like JavaScript’s array methods.
In contrast to JavaScript’s array methods, collections have a lot more methods available making your code a lot simpler. Here are basic examples using a collection:
const User = require('../models/user')
const Collect = require('@httpie/collections')
const users = await User.findAll()
const notSubscribedUsers = Collect(users)
.filter(user => {
return user.notSubscribedToNewsletter
})
.all()
// notSubscribedUsers = [ <list of not-yet-subscribed users> ]
Here’s another example outlining how to determine whether the array “has” an item:
// “has” in JS Arrays
const hasNotSubscribedUsers = !![].concat(users).find(user => {
return user.notSubscribedToNewsletter
})
// “has” in Collections
const hasNotSubscribedUsers = Collect(users).has(user => {
return user.notSubscribedToNewsletter
})
All available methods are outlined in the docs.
The package is async/await-ready and supports async callback functions. A collection becomes async (returns a promise) as soon as you provide an async callback method to methods like map, filter, find, and so on. You then need to await the collection pipeline:
const User = require('../models/user')
const Collect = require('@httpie/collections')
const users = await User.findAll()
const subscribedUsers = await Collect(users)
.filter(user => {
return user.notSubscribedToNewsletter
})
.map(async user => { // <-- providing an async callback creates an async collection that you need to `await`
await user.subscribeToNewsletter()
return user
})
// subscribedUsers = [ <list of newly-subscribed users> ]
You can directly await async collections without ending the call chain with .all(). You can still call .all() though, it works as well.
Do you miss a collection function? We very much appreciate your contribution! Please send in a pull request 😊
git checkout -b my-featuregit commit -am 'Add some feature'git push origin my-new-featureMIT © Supercharge
httpiejs.com · GitHub @httpie · Twitter @httpiejs
FAQs
HTTPie collections
We found that @httpie/collections demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.