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

@corejam/cli

v0.0.26

Published

Corejam CLI package.

Downloads

41

Readme

Corejam

Usage

Corejam is a scaffolding for building progressive GraphQL powered jamstack applications.

npm i -g @corejam/cli

To get started with a new project, run the following command:

corejam createApp <NAME>    # create new project
cd <NAME>                   # change into project directory
corejam dev                 # start the corejam dev playground

# GraphQL playground will be available on localhost:3000
# StencilJS playground will be available on localhost:3001

Documentation

  Usage
    $ corejam <command> [options]

  Available Commands
    build             Build the whole plugin source
    dev               Plugin dev process
    api:serve         Start graphql Server
    api:dev           Start graphql server and set up hot reloading
    createApp         Bootstraps new corejam app
    generateSchema    
    test              
    test:wc           
    static            build static html from app
    static:serve      Serve static folder

  For more info, run any command with the `--help` flag
    $ corejam build --help
    $ corejam dev --help

  Options
    -v, --version    Displays current version
    -h, --help       Displays this message
   

Env vars (move to correct package)

We need to define different env variables for the following use cases: dev, pre-render (static html), ssr (production)

Dev, static: client url has to be prefixed because we are running on 2 different ports (3001 stenciljs, 3000 api). Client url has to be prefixed for client bundle + hydration.

Production: url has to be prefixed with absolute url for hydration. Client bundle without prefix due to same origin