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

@creuna/cli

v3.3.0

Published

Creuna command line tools

Downloads

58

Readme

Creuna CLI

npm version Travis status

@creuna/cli provides a unified interface for:

Install

yarn global add @creuna/cli

or

npm install -g @creuna/cli

Usage

Print help:

creuna

Run commands:

creuna <command>

Commands

new <relative-path>

Creates a new React app in the current working directory. If a path is provided, files will be written to this path, relative to the current working directory

lib

Select and download components from the React component library.

component <name>

Create empty React component in your components folder.

page <name> <human-readable-name> <group-name> <url>

Create empty static site page component in your static site pages folder (Useful if you're working with an app created with the new command)

rename <old-name> <new-name>

Rename React component. Supports absolute path or path relative to componentsPath.

stateful <component-name>

Convert React component to stateful. Supports absolute path or path relative to componentsPath

stateless <component-name>

Convert React component to stateless if able to. Supports absolute path or path relative to componentsPath

Notes

All commands except creuna new support a .creunarc.json in your project root. Having this file ensures that components are always added to the correct folder, regardless of your current directory (within the project of course). The boilerplate app created by creuna new includes this file. dataFileExtension and dataFileContent control the static data file generated by the creuna page command.

.creunarc.json

{
  "componentsPath": "relative/path/to/components",
  "staticSitePath": "relative/path/to/static/site/pages",
  "dataFileExtension": "js",
  "dataFileContent": "export default { a: 'a' };"
}

Custom static page template

A custom template can be added that will be used when running creuna page. The template can be added in .creunarc.json as staticPageTemplate which must be an array of strings (one string per line). @babel/template syntax (see here) is used to insert the correct component name and data file path. The tokens %%componentName%% and %%dataFilePath%% are used for this and they must be included at least once each. Example:

{
  "staticPageTemplate": [
    "import React from 'react';",
    "import content from %%dataFilePath%%;",
    "const %%componentName%% = () => <div />;",
    "export default %%componentName%%;"
  ]
}