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

@nimbella/nimbella-cli

v4.2.8

Published

A comprehensive CLI for the Nimbella stack

Downloads

1,858

Readme

About Nimbella.

We're building a beautiful cloud so your experience is delightful, one that allows you to focus on what you do best: explore idea, create value, and deliver applications that you are proud of. We are excited to see what you will build today, and we want to hear from you: what worked, what didn't, what we can do better — after all, we are not done and there is more to come. Reach us on Slack or on GitHub. Your Nimbella cloud account gives you all of the following features and benefits:

  • A dedicated and secure domain name for your cloud applications. If you need more, let us know.
  • Static front-end assets are automatically deployed to and served from a global CDN.
  • Back-ends are run on demand, near-instantly. No servers for you to be bothered with, ever.
  • Upload files to a secured data bucket, grant limited access as needed.
  • Record application state in a key-value store, with data accessible to all your back-end logic at extremely low latency.
  • Build workflows and orchestrate long running tasks.

This repository contains the source to our nim command line tool. It is possible to contribute. See our contribution guide.

Development

Building the project code

To build the code, run the following commands from the project directory.

npm install
npm pack

Testing in development

If you need to run commands using the local version of the project during development - once you have built the project source code - run the following command:

./bin/run <nim commands>

Remember to re-build the project (tsc -b) after making changes before testing.

Distribution of the package

The build process above gives you a tarball that can be installed globally or used as a dependency on the machine on which it was built. It is not suitable for publication. To obtain a tarball that can be used more widely:

  1. After building in deployer publish the result somewhere (publish to npm, place in a web bucket, make it available as static content to a web server, etc.)
  2. Change the dependency on nimbella-deployer in package.json to reference the published version.
  3. Complete the build.

The current build will create a version of nim suitable for use with services on nimbella.io. It presumes the runtime repertoire that is present there, and uses the "error page" (404.html) that is used on nimbella.io. You can change these things by placing your own files runtimes.json or 404.html in the deployer directory.

Brew formula

For every release the github workflow updates the brew formula in nimbella/brew repo.

Node version update:

When node dependency version is updated in package.json, run npm run pack, make a fresh release and run

node release/homebrew/homebrew.js

It updates nimbella and nimbella-node formulas in nimbella/brew repo.