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

clixor

v1.0.2

Published

A modern CLI for initializing and managing development projects

Downloads

3

Readme

🚀 Clixor

Version License PRs Welcome

Streamline your project setup with Clixor - the modern CLI for effortless development initialization.

InstallationUsageFeaturesContributingSupport


🌟 Features

  • 🏗️ Project Initialization: Quickly bootstrap projects using predefined or custom templates
  • 🎨 Customizable Templates: Easily manage and use your own project templates
  • 🧭 Interactive Setup: User-friendly prompts guide you through project configuration
  • 📦 Multiple Package Managers: Seamless support for npm, Yarn, and Bun
  • 🛠️ Optional Tooling: Integrate popular tools like ESLint, Prettier, Jest, and Docker with ease
  • ⚙️ Flexible Configuration: Persist and manage your preferences for future use

🚀 Quick Start

npx clixor init my-awesome-project

This command initializes a new project named "my-awesome-project" using Clixor's interactive setup.

📦 Installation

Prerequisites

  • Node.js (v14 or later)
  • Git

Steps

  1. Clone the repository:

    git clone https://github.com/Youssefbaghr/Clixor.git
    cd Clixor
  2. Install dependencies:

    npm install
    # or
    yarn install
    # or
    bun install
  3. Link the CLI globally:

    npm link

🖥️ Usage

Initialize a New Project

clixor init

Follow the interactive prompts to configure your project.

Manage Configuration

clixor config --list
clixor config --set templateDir=/path/to/templates
clixor config --reset

Manage Templates


clixor template --list
clixor template --add react-ts https://github.com/example/react-ts-template.git
clixor template --remove react-ts

🛠️ Configuration

Clixor uses a JSON configuration file stored at ~/.Clixor-config.json. You can edit this file directly or use the clixor config command.

Example configuration:

{
  "defaultTemplate": "react",
  "packageManager": "npm",
  "features": ["eslint", "prettier"],
  "customTemplates": {
    "react-ts": "https://github.com/example/react-ts-template.git"
  }
}

🧩 Extending Clixor

Creating Custom Templates

  1. Create a Git repository with your project structure
  2. Add a clixor.json file to specify template options:
    {
      "variables": ["projectName", "author"],
      "scripts": {
        "post-init": "npm run setup"
      }
    }
  3. Add the template using clixor template --add

Creating Plugins

Clixor supports a plugin system that allows you to extend its functionality. Here's how to create a plugin:

  1. Create a new TypeScript file in the src/plugins directory.
  2. Import the PluginInterface from src/plugins/types/index.ts.
  3. Create a class that implements the PluginInterface.
  4. Implement the required methods:
    • name: A string identifier for your plugin.
    • version: The version of your plugin.
    • initialize: A method called when the plugin is registered.
    • execute: The main functionality of your plugin.

Example plugin:

import { PluginInterface } from '../types';
export class MyCustomPlugin implements PluginInterface {
name = 'MyCustomPlugin';
version = '1.0.0';
initialize(): void {
console.log('MyCustomPlugin initialized');
}
async execute(context: any): Promise<string> {
return MyCustomPlugin executed with context: ${JSON.stringify(context)};
}
}

To use your plugin, register it in the src/utils/plugins.ts file:

import { MyCustomPlugin } from '../plugins/MyCustomPlugin';
// In the loadPlugins function
const myCustomPlugin = new MyCustomPlugin();
myCustomPlugin.initialize();
// Add logic to use the plugin as needed

Plugins allow you to add new commands, modify existing functionality, or integrate with external services to enhance Clixor's capabilities.

🤝 Contributing

We love our contributors! ❤️ Check out the CONTRIBUTORS.md file to see the amazing people who have helped make Clixor awesome.

Want to join this list of amazing people? We'd love your help! Here's how you can contribute:

  1. 🍴 Fork the repository
  2. 🌿 Create a new branch
  3. ✨ Make your changes
  4. 🔧 Test your changes
  5. 📤 Submit a pull request

For more detailed information, please read our Contributing Guide.

Whether it's submitting a bug report, proposing a new feature, or improving documentation - every contribution counts!

📜 Changelog

See CHANGELOG.md for a history of changes to this project.

📄 License

This project is licensed under the MIT License - see the LICENSE file for details.

🙏 Acknowledgements