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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@scalecube/scalecube-js

v0.0.6

Published

Scalecube-js provides microservices pattern, in easy to use way. Supporting NodeJS and Browers (your client doesn't have to be mono!)

Downloads

27

Readme

Scalecube-js

First version for scalecube js Implemented only the Microservices basic pattern only local services without remote services (no gossip or SWIM) Support CommonJS and ES6 modules with TS & Flow support

First version documention will improve ;-)

usage

/// With proxies

const greetingService = Microservices
  .builder()
  .services(new GreetingService(), new GreetingService())
  .build()
  .proxy()
  .api(GreetingService)
  .create();  
greetingService.hello();

const greetingService = Microservices
  .builder()
  .services(new GreetingService(), new GreetingService())
  .build()
  .proxy()
  .api(GreetingService)
  .create();
greetingService.repeatToStream().subscribe(...);

/// direct 
const microservices = Microservices.builder()
  .services(new GreetingService())
  .build();

const dispatcher = microservices.dispatcher().create();

const message: Message = {
  serviceName: 'GreetingService',
  method: 'hello',
  data: {user: 'Idan'}
};


dispatcher.invoke(message);

const microservices = Microservices.builder()
  .services(new GreetingService())
  .build();

const dispatcher = microservices.dispatcher().create();

const message: Message = {
  serviceName: 'GreetingService',
  method: 'repeatToStream',
  data: [ 'Hello', 'Hey', 'Yo' ]
};

dispatcher.listen(message).subscribe();

/// loaders

// on demand
const greetingService = Microservices
.builder()
.serviceLoaders(
  {
    loader: () => ({
      then: (func) => {
        ImportGreetingService
          .then((GreetingService) => func(new GreetingService.default()))
      }
    }),
    serviceClass: GreetingService
  })
.build()
.proxy()
.api(GreetingService)
.create();

// on start
const greetingService = Microservices
.builder()
.serviceLoaders(
  {
    loader: () => new Promise((resolve, reject) =>
      ImportGreetingService.then((GreetingService) => resolve(mockFn(GreetingService))).catch(e => reject(e))
    ),
    serviceClass: GreetingService
  })
.build()
.proxy()
.api(GreetingService)
.create();

For more details how to use it see the tests

Run/Debug

Install yarn/npm install
Build npm build
Run test npm test

To run/debug jest tests:

  • jest options: --runInBand --no-cache --env=jsdom
  • env variables: BABEL_ENV=commonjs
  • you can run/debug via Webstorm or npm test or directly with jest and debug with Chrome: https://facebook.github.io/jest/docs/en/troubleshooting.html image

Version

  • http://semver.org/ format

MAJOR version when you make incompatible API changes,

MINOR version when you add functionality in a backwards-compatible manner, and

PATCH version when you make backwards-compatible bug fixes.