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

@aptoma/dredition-cli

v1.7.0

Published

DrEdition CLI

Downloads

157

Readme

DrEdition CLI

Installation

npm install @aptoma/dredition-cli

Can also be installed globally:

npm install -g @aptoma/dredition-cli

Usage

DrEdition layoutpreview

Live reload

dredition layoutpreview live-reload

Should be called at the root of your assets directory. An example of an expected structure looks like this:

.
├── stylesheets
    ├── **/*.scss
│   └── styles.scss
└── templates
    └── components
        ├── headline
        │   ├── headline.html
        │   └── headline.scss
        ├── intro
        │   ├── intro.html
        │   └── intro.scss
        └── componentName
            ├── componentName.html
            └── componentName.scss

The first time the script is run, you will be asked to configure everything. The config file will be default be stored in ~/.aptoma/dredition/config.json.

If you are a developer and want to run live-reload with a dev environment, you'll have to edit config.json manually. The automated setup will only work for production use.

Example custom setups of config.json

Override urls for all configs:

{
    "default": {
        "frontendUrl": "https://{account}.dredition-dev.aptoma.no",
        "apiUrl": "https://dredition-api-dev.aptoma.no",
        "assetBuilderUrl": "https://asset-builder.dev.ecs.aws.aptoma.no"
    },
    "broadcast": {
        "account": "broadcast",
        "apikey": "secret"
    },
    "aptoma": {
        "account": "aptoma",
        "apikey": "secret"
    }
}

Override urls for only a specific config:

{
    "broadcast": {
        "account": "broadcast",
        "apikey": "secret",
    },
    "broadcast-dev": {
        "account": "broadcast",
        "apikey": "secret",
        "frontendUrl": "https://{account}.dredition-dev.aptoma.no",
        "apiUrl": "https://dredition-api-dev.aptoma.no",
        "assetBuilderUrl": "https://asset-builder.dev.ecs.aws.aptoma.no"
    }
}