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 🙏

© 2025 – Pkg Stats / Ryan Hefner

ngx-reverse-rest

v2.1.0

Published

The Angular REST library that thinks differently.

Downloads

10

Readme

ngx-reverse-rest

The Angular REST library that thinks differently.

Leightweight, fully tested and as flexible as it could be (with DI in its heart).

Build Status Coverage Status

What it is about

Terms:

  • REST Service - an Angular service that performs the communication with the REST endpoint
  • DTO (Data Transfer Object) - a class that represents a data being sent (similar to gRPC message)

Most of the REST libraries in the wild look at the communication with REST endpoints from services prospective. Every endpoint gets a corresponding Angular service. Every service sends / receives the DTOs.

This library attempts to reverse this idea. Mostly, while developing, one does not care about the different REST services. One cares about the DTOs, so here the DTO holds all information that is required for getting / sending this DTO.

Installation

npm i ngx-reverse-rest

Usage

1. Add module to the app.module.ts

imports: [
  // ...
  ReverseRestModule,
  // ...
]

2. BackendService

Create a REST Service that will be (most likely) the only one you have:

import { HttpClient } from '@angular/common/http';
import { Injectable } from '@angular/core';
import { map } from 'rxjs/operators';
import { ReverseRestClass, ReverseRestRequest, ReverseRestUtils } from 'ngx-reverse-rest';

@Injectable({
  providedIn: 'root'
})
export class BackendService {

  constructor(
    private http: HttpClient,
    private utils: ReverseRestUtils,
  ) { }

  getArray<T>(clss: ReverseRestClass<T>, params: ReverseRestRequest = {}) {
    return this.http.get<T[]>(this.utils.resolveUrl(params), this.utils.getHttpOptions(params))
      .pipe(map(r => r.map(i => new clss(i))));
  }

  get<T>(clss: ReverseRestClass<T>, params: ReverseRestRequest = {}) {
    return this.http.get<T>(this.utils.resolveUrl(clss, params.path), this.utils.getHttpOptions(params))
      .pipe(map(r => new clss(r)));
  }

  put<T>(object: T, params: ReverseRestRequest = {}) {
    return this.http.put(this.utils.resolveUrl(params), object, this.utils.getHttpOptions(params))
      .pipe(map(r => new (this.utils.resolveClass(object))(r)));
  }

  post<T>(object: T, params: ReverseRestRequest = {}) {
    return this.http.post(this.utils.resolveUrl(params), object, this.utils.getHttpOptions(params))
      .pipe(map(r => new (this.utils.resolveClass(object))(r)));
  }

  delete(params: ReverseRestRequest) {
    return this.http.delete<void>(this.utils.resolveUrl(params), { params: params.query, headers: params.headers });
  }

}

3. Describe your entities

For each of your DTOs add the endpoint describing where you get them from / send them to:

import { ReverseRestEntity } from 'ngx-reverse-rest';

@ReverseRestEntity({
  urls: [
    '/api/rest/v1/entities',
    '/api/rest/v1/entities/:id',
    '/api/rest/v1/entity-groups/:groupId/entities',
    '/api/rest/v1/entity-groups/:groupId/entities/:id'
  ],
})
class ExampleEntity {
  id: string;
  name: string;

  constructor(options: Partial<ExampleEntity> = {}) {
    this.id = options.id;
    this.name = options.name;
  }
}

Here the users could be received from different endpoints.

4. Send and receive

See app.component.ts in this project:

import { Component, OnInit } from '@angular/core';
import { BackendService } from './backend-service';

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.scss']
})
export class AppComponent implements OnInit {

  constructor(private backend: BackendService) {
  }

  ngOnInit() {
    // get by auxiliary path parameter
    this.backend.getArray(ExampleEntity, { path: { groupId: 'example-group' } }).subscribe(entities => {
      console.log(entities.map(entity => entity.name));
    });

    // create
    this.backend.post(new ExampleEntity()).subscribe(entity => {
      console.log(entity.name);

      entity.name = 'new name';

      // update
      this.backend.put(entity).subscribe(updatedEntity => {
        console.log(updatedEntity.name);

        // delete
        this.backend.delete({ path: { id: updatedEntity } });
      });
    });
  }

}

License

MIT