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

@drarig29/modular-cli

v0.0.6

Published

- The core of the CLI should be minimal. <!-- XXX: not sure about this actually. - Nothing else than commands should be exported from each plugin. - Anything exported from `modular-cli` should be directly available, not through plugins. A plugin should ne

Downloads

13

Readme

modular-cli

  • The core of the CLI should be minimal.

Running modular-cli <command> <anything> requires a plugin named @drarig29/modular-cli.plugin-<command>

Supported ways to use it:

  • With Node.js
    • [x] npm i -g @drarig29/modular-cli <command> (installed globally)
      • Downloads the required plugin, and saves it for future executions.
      • Note: Can be run with modular-cli <command>
      • Note: Doesn't load plugins installed globally with npm i -g @drarig29/modular-cli.plugin-<command>
    • [x] npx @drarig29/modular-cli <command> (not installed, run from any non-project folder)
      • Downloads the required plugin, and saves it for future executions.
      • Note: Doesn't load plugins installed globally with npm i -g @drarig29/modular-cli.plugin-<command>
    • [x] npx @drarig29/modular-cli <command> (not installed, run from a project)
      • Downloads the required plugin, and saves it for future executions.
      • Note: Doesn't load plugins installed locally with npm i -g @drarig29/modular-cli.plugin-<command>
    • [x] npx @drarig29/modular-cli <command> (run from a project where it's installed)
      • Loads the required plugin if it's installed locally with npm i @drarig29/modular-cli.plugin-<command>
      • Otherwise, downloads the required plugin, and saves it for future executions.
    • [ ] npx @drarig29/modular-cli plugins import [<name> ...] (run from a project where it's installed)
      • This will save all requested plugins locally into a .modular-cli/plugins folder, you should commit this folder.
      • npx @drarig29/modular-cli <command> will load the required plugin from that folder.
      • Note: Installing the plugins in such a way results in a smaller installation footprint as the plugins are minimized.
      • Note: Running the command without any plugin name will detect a configuration file, and guess the plugins to install.
  • Without Node.js
    • [x] A standalone executable (roughly the size of Node.js itself) must be downloaded with curl
      • Downloads the required plugin, and saves it for future executions.

Note: .modular-cli is called a portable path.

References:

  • https://github.com/yarnpkg/berry/blob/daa574791b3b2df01e76c1fdfd9c975050a0fb9d/packages/yarnpkg-builder/sources/commands/build/plugin.ts
  • https://github.com/yarnpkg/berry/blob/daa574791b3b2df01e76c1fdfd9c975050a0fb9d/packages/yarnpkg-builder/sources/commands/new/plugin.ts#L6
  • https://github.com/yarnpkg/berry/blob/daa574791b3b2df01e76c1fdfd9c975050a0fb9d/packages/plugin-essentials/sources/commands/plugin/list.ts#L6
  • https://raw.githubusercontent.com/yarnpkg/berry/master/plugins.yml
  • https://github.com/yarnpkg/berry/blob/daa574791b3b2df01e76c1fdfd9c975050a0fb9d/packages/plugin-essentials/sources/commands/plugin/import.ts#L123
  • https://github.com/yarnpkg/berry/blob/master/packages/docusaurus/docs/advanced/04-technical/plugin-tutorial.md
  • https://github.com/yarnpkg/berry/blob/daa574791b3b2df01e76c1fdfd9c975050a0fb9d/packages/yarnpkg-cli/sources/tools/getDynamicLibs.ts#L19-L22
  • https://github.com/yarnpkg/berry/blob/daa574791b3b2df01e76c1fdfd9c975050a0fb9d/packages/yarnpkg-core/sources/Configuration.ts#L1110-L1379
  • https://github.com/yarnpkg/berry/issues/1678#issuecomment-669873299