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

electrode-native

v1.1.1

Published

Electrode Native Global CLI

Downloads

81

Readme

Electrode Native Global CLI

This is a node project meant to be installed globally on the user workstation through :

npm install -g electrode-native

This will make the ern binary available globally.

The job of this binary is solely to bootstrap the platform and also proxy all commands to the local client of the currently activated platform version.

These two responsibilities can be summarized as follow :

  • Bootstrapping : Whenever the user run ern command for the first time ever on his/her workstation, the global client will create the platform folders and initial configuration file and will install the latest platform version.

  • Proxy to local client : If there is at least a version of the platform installed, this global client will just act as a proxy to the local client (ern-local-cli) of the currently activated platform version.

If you have to work on this client, you can run npm link from this folder, then access ern as a normal user would.

This project should hopefully never be modified. We really really don't want to ask users to update this global client. The local client should be modified instead.

That being said the global client will check for updates every 24 hours. If an updated version is available, it will inform the user that a new version is available and give him the instructions to update the client.

For example, here is how the current notification looks like :

╭────────────────────────────────────────────────────────────╮
│                                                            │
│              Update available 0.0.3 → 0.0.4                │
│          Run npm i -g electrode-native to update           │
│                                                            │
╰────────────────────────────────────────────────────────────╯

We cannot assume however that every user will update, therefore, updates of the global client should maintain backward compatibility.