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

press-cli

v0.0.3

Published

CloudPresser's all-inclusive React Native command line tool.

Downloads

287

Readme

Press-cli

Press was made to be a tool to help you rapidly develop with typescript, react-native ~~, graphql and serverless functions~~.

It achive this by giving you a quick way to:

  • Have a project up with database, api and supporting serverless functions without writing boilerplate or extensive configuration
  • Enjoy awesome development support features and skip boilerplate code by generating new aspects of your application such as screens, components, ~~scripts and serverless functions~~ using completely customizable and extensible generator templates
  • WIP: Deploy your project's infrastructure in minutes with preconfigured services, and customizable options using or developing your own plugins

Getting started

  • ~~Have docker installed~~

    • No docker knowledge needed, it just runs in the background!
    • How to install docker docs here...
  • Install press

    • yarn global add press-cli
  • Create a new project

    • press new $projectName
  • Go to your new project

    • cd $projectName
  • Start developing

    • yarn start

And you have a new mobile app running with react native, ~~postgres database, graphql api and serverless functions~~ ready to be developped with generators for all of them!

WIP: File Structure

/project_name
|---/package.json
|---/press.json ? => configuration for each plugin
|---/mobile
|---/web
|---/shared
|---|---/utils
|---|---/scripts
|---|---/models
|---/functions
|---/press
|---|---/templates
|---|---|---/mobile
|---|---|---|---/screen
|---|---|---|---/component
|---|---|---/web
|---|---|---/shared
|---|---|---|---/utils
|---|---|---|---/scripts
|---|---|---|---/models
|---/functions
|---/node_modules *ignored
|---/db_data *ignored
|---/files *ignored

Commands

  • press generate $generator_name $instance_name
    • scans generators for folder of $generator_name
      • if found, outputs evaluates template inside /project_name/press/templates using $instance_name and outputs to relative path inside /project_name
    • if $generator_name === list, press will output all available generators
  • press new $project_name
    • Creates a new Press project
  • WIP: press start $plugin_name
    • runs configured start command for specified plugin inside plugin folder
    • start command must be configured inside press.json
    • if no $plugin_name, it will start all plugins
  • WIP: press develop $plugin_name
    • runs configured develop command for specified plugin inside plugin folder
    • develop command must be configured inside press.json
    • if no $plugin_name, it will run the develop for all plugins
  • WIP: press deploy $plugin_name
    • deploys specified plugin to production
    • if no $plugin_name, it will deploy all plugins
  • WIP: press install $plugin_name
    • installs a press plugin
    • press plugins are hosted on npm and package name must start with press
    • installing a plugin will scaffold the plugin inside your press project
  • WIP: press eject $plugin_name
    • outputs a plugin's default generators to the root of your press project
    • generators can now be edited as needed

WIP: Plugins

Plugins are distinct aspects of a press application. A plugin is a way for developers to bring their own needs into press