npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@lexxsoft/odata-http-query

v1.0.3

Published

Creating and parsing URL query for OData and more

Downloads

11

Readme

@lexxsoft/odata-http-query

GitHub package.json version GitHub GitHub all releases

Contents

Installation

npm i @lexxsoft/odata-http-query

Usage

Basic usage

const o: QueryBuilder = new QueryBuilder()

or

const o: QueryBuilder = QueryBuilder.make()

Or create with flow

const o: string = QueryBuilder.make()
    .querySet('lang', 'en')
    .toString()

Output lang=en

Configuration

QueryBuilder has configuration to customize process.

Markers

QueryBuilder has markers to customize fixed query params. Type for markers shown below:

type TQueryMarkers = {
    select: string[] | string,
    limit: string[] | string,
    offset: string[] | string,
    order: string[] | string,
    expand: string[] | string,
    search: string[] | string,
    count: string[] | string,
    filter: string[] | string,
}

Markers and corresponding query field

By default, QueryBuilder markers are correspond to OData query field.

const DefaultQueryMarkers: TQueryMarkers = {
    limit: ['$top', '$limit'],
    offset: ['$skip', '$offset'],
    order: ['$orderby', '$order'],
    expand: '$expand',
    select: '$select',
    filter: '$filter',
    count: '$count',
    search: '$search',
}

Of course, you can customize there names as you need. For flexibility each marker could have alias. Pass them as array to defaults for correct work. Look at example above.

Custom configuration

QueryBuilder configuration type:

type TQueryBuilderDefaults = {
    limit?: number,
    markers?: TQueryMarkers,
}

| Field | Type | Default | Description | |---------|---------------|-----------------------|-----------------------------------------------------------| | limit | Number | undefined | Set limit to use limitation for every builder instance. | | markers | TQueryMarkers | DefaultQueryMarkers | Set custom query field name for every marker |

Ordering

Use order method to add order query parameters

Note: order method has an alias orderby

const o = new QueryBuilder()
o.order(new QueryOrder('name1')).toString()

Output $orderby=name1 asc

Also, you can combine several order conditions

const o = new QueryBuilder()
o.order(new QueryOrder('name1')).order(new QueryOrder('name2', QueryOrderDirection.DESC))
o.toString()

Output $orderby=name1 asc,name2 desc

Expanding

Use expand method to add expand query parameter

const o = new QueryBuilder()
o.expand('company').toString()

Output $expand=company

Or combine several expand parameters

const o = new QueryBuilder()
o.expand('company').expand('jobtitle').toString()

Output $expand=company,jobtitle

To add counter to expanding parameter, add true as second parameter of expand method

const o = new QueryBuilder()
o.expand('emails', true).toString()

Output $expand=company($count=true)

Limiting

For limiting returned data, use limit and offset methods

Note: limit has an alias top offset has aliases skip and shift

const o = new QueryBuilder()
o.top(7).skip(4).toString()

Output $top=7&$skip=4

Filtering

Use filter method to add constrains. QueryBuilder accept only one filter, but you free to use and and or methods of QueryFilter to combine them together.

const oFilter = new QueryFilter('gender', 'f')
oFilter.and('age', 16, QueryFilterSign.GT)
const o = new QueryBuilder()
o.filter(oFilter).toString()

Output $filter=gender eq f and age gt 16

Filter operations

  • [X] EQ
  • [X] GT
  • [X] GE
  • [X] LT
  • [X] LE
  • [ ] NE
  • [X] SUBSTRINGOF
  • [X] STARTSWITH
  • [X] ENDSWITH

Counting

count method will add $count suffix to url

const o = new QueryBuilder()
o.count().toString()

Or use inlineCount and get same result

const o = new QueryBuilder()
o.inlineCount()

Output $count=true

Of course, you can use count with filter for example.

const oFilter = new QueryFilter('gender', 'f')
oFilter.and('age', 16, QueryFilterSign.GT)
const o = new QueryBuilder()
o.filter(oFilter).count().toString()

Output $count=true&$filter=gender eq f and age gt 16

Select

Use select method to constrain returned fields

const o = new QueryBuilder()
o.select(['id', 'name']).toString()

Output $select=id,name

search

Free-text search parameter, which was added for OData v4.0

const o = new QueryBuilder()
o.search('John Doe')

Output `$search=John Doe

Parsing URL

For case if you already have url, and you want to add or change some parameter, you may use parse method, to parse url and get instance of QueryBuilder

const o = QueryBuilder.parse(`/users?$count=true`)
consle.log(o.toString())

Output $count=true

Making URL

To create URL use method toUrl. As base URL use any URL-like string without query parameters.

const o = QueryBuilder.make()
    .filter('name1', 'John')
consle.log(o.toUrl('/users'))

Output /users?$filter=name1%20eq%20'John'