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

aksell-cli

v2.9.5

Published

A command line tool for Aksell organization

Downloads

9

Readme

A Command Line Tool for Aksell organization

Dependencies

Commands

yml [options] Create a Github workflow with React build and FTP output
help [command] display help for command

YML Arguments:

-o --output <output> Specify a output folder (e.g. ./react-project)
-s --server <server> Specify a server (e.g. 215/213)
-sd --serverDir <server> Specify a directory on the server (e.g. 358109)
-h, --help display help for command

CRA Arguments:

-n --name <output> Specify a project name (e.g. nav-kalkulator)
-h, --help display help for command

UMB Arguments:

-n --name <output> Specify a project name (e.g. nav-kalkulator)
-h, --help display help for command

GH Arguments:

-n --name <output> Specify a repo name (e.g. aks_cra_nav-kalkulator)
-h, --help display help for command

UMB post-install setup

On install the umbraco instance runs automagically.

To start the project from CLI:

  • cd into project folder
  • run the command "dotnet run"

The terminal output will tell you the URL to access the site.

Some extra setup is required to get up and running with the UMB template

  • Install Umbraco backoffice and set up database
  • In backoffice settings => Document types: Import "01_SEO.udt" and "02_Website.udt" document types (NB the order of import matters! Import SEO first and then Website) These files are found in the "ASSETS" folder in the umbraco project folder
  • In backoffice settings => Templates: Create a template called "Website". The content of this template should be auto generated based on the Website document type.
  • In backoffice settings => Document types: Select the Website template and set it as default
  • In backoffice content: Create a Root site and select Website as template
  • Save and publish the root site and you should be good to go

Next step is probably to add the project to git