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

@vsaas/loopback-connector-remote

v11.0.2

Published

Fork of LoopBack 3 remote connector for connecting to REST APIs and other remote services from LoopBack apps

Readme

@vsaas/loopback-connector-remote

@vsaas/loopback-connector-remote is a maintained fork of loopback-connector-remote for the Xompass LoopBack 3 stack.

The goal of this fork is practical compatibility with existing LoopBack 3 applications while simplifying the package and aligning it with the rest of the modernized @vsaas/* ecosystem.

What Changed In This Fork

  • Runtime migrated to TypeScript-backed sources and built to dist/
  • Tooling aligned with the other forks:
    • tsdown
    • vitest
    • oxlint
    • oxfmt
  • Legacy test/build infrastructure removed:
    • grunt
    • mocha
    • old ESLint/JSHint config
  • Avoidable development dependencies removed
  • Package metadata and exports aligned with the scoped @vsaas/* packages

This package is intended for the Xompass-maintained LoopBack 3 forks. It is not targeted at LoopBack 4.

Installation

npm install @vsaas/loopback-connector-remote

In practice this connector is usually installed alongside:

  • @vsaas/loopback
  • @vsaas/loopback-datasource-juggler
  • @vsaas/remoting

Usage

Configure a datasource with the remote connector:

{
  "myRemoteDataSource": {
    "name": "myRemoteDataSource",
    "connector": "remote",
    "url": "http://localhost:3000/api"
  }
}

Or in code:

const loopback = require('@vsaas/loopback');

const app = loopback();

const ds = app.dataSource('remote', {
  connector: require('@vsaas/loopback-connector-remote'),
  url: 'http://localhost:3000/api',
});

After attaching a compatible remote model, the connector proxies the remote methods through LoopBack models and preserves promise-based usage:

const result = await app.dataSources.remote.models.MyModel.findById(1);

Public Exports

  • @vsaas/loopback-connector-remote
  • @vsaas/loopback-connector-remote/relations

Development

npm run typecheck
npm run lint
npm test

Notes

  • This fork keeps compatibility with common LoopBack 3 remote-model behavior.
  • Error messages and maintenance decisions in the Xompass forks are kept in English only.
  • If you are using this package outside the Xompass forked stack, verify the exact versions of @vsaas/loopback, @vsaas/loopback-datasource-juggler and @vsaas/remoting you want to pair with it.