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

atomable-runtime

v1.0.0-alpha.13

Published

Runtime for atomable's serverless microservice framework.

Downloads

25

Readme

atomable npm Build Status

atomable runtime

This is the runtime for the atomable serverless microservices framework. Our goal is to make your serverless life easier!

The best way to use this runtime is by using our insanely powerful atomable cli.

If using command line tools is not your thing, well we still got your covered! Check out the code examples below to get started!

Documentation

https://docs.atomable.io/

Source code | fork | pull request | issues

https://github.com/atomable/runtime

Installation

npm

npm install atomable-runtime

yarn

yarn add atomable-runtime

Importing

const runtime = require('atomable-runtime');

import { register, handle } from 'atomable-runtime';

Usage

To use the runtime you need to create an AWS lambda that will be the main entry point of your project. Once this is done, you never have to think about configuring more lambdas.

handler.js

const runtime = require('atomable-runtime');

/**
 * () registers the function and the
 * callback to handle the aws event
 */
(() => {
  const protonHandler = require('./proton/proton.js').proton;
  const protonConf = { name: 'proton', https: { path: 'proton', method: 'get', parameters: [{ in: 'query', name: 'firstName' }, { in: 'query', name: 'lastName', required: false }] }};
  runtime.register(protonHandler, protonConf);

  const electronHandler = require('./electron/electron.js').electron;
  const electronConf = { name: 'electron', https: { path: 'electron', method: 'post', parameters: [{ in: 'body', name: '*' }, { in: 'headers', name: 'authorization' }] }};
  runtime.register(electronHandler, electronConf);
})();


/**
 * handler() handles aws lambda events
 */
export const handler = runtime.handle;

proton.js

// firstName is guaranteed not to be null since it is required by default
// since we configured lastName to not be required, it may be undefined here
module.exports.proton = (firstName, lastName) {
  // you can also return a promise, we will handle the result correctly.
  return { statusCode : 200, body: `Hello ${firstName} ${lastName}` };
};

Tests

To run the tests, simply checkout the code and run npm test.

Contributing

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request!

If you find issues with the runtime, log them here in our issues.

If you feel like contributing, one thing you have to know is we hate classes, the keyword new and we like to use our Monad library, lift.js, as often as possible :)

Roadmap

Here is a list of things we want to do in this project, feel free to help us out!

  • Add parameter validators (stringNotEmpty, stringLength, intBetween, etc. That sort of thing...)
  • Better error messages when things are not configured as they should.
  • Support multiple cloud providers

Links

License

MIT