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

cultum-fe-starter-kit

v1.1.3

Published

The base Cultum template

Downloads

3

Readme

Cultum Front-end Starter Kit

Basic project structure organizations and start point for a new project

Getting Started

~ Clone project into your local projects folder:

git clone [email protected]:Venumteam/cultum-fe-starter-kit.git

~ Open cloned project in the IDE

*deploy information goes here

Basic flow example:

  • MR's should be created to develop branch
  • When merged, release branch can be created and merged to the master branch
  • To deploy staging master should be merged to the staging
  • To deploy production staging should be merged to the production branch

Prerequisites

To work on this project you should install:

  • IDE - code editor
  • git - version control system
  • nvm - node version package manager
  • nodejs - check nvmrc file in the root to get the right version and install package via nvm
  • yarn - package manager

default API or local ports you can find in the .env.example

Installing

Steps to run application in the DEV environment:

  1. yarn - install all required packages
  2. copy .env.example.local to the root and create .env.local file
  3. yarn dev - run local server

Steps to run application in PROD environment:

  1. 1 & 2 steps from the steps above, if not already used
  2. yarn build - builds the project
  3. yarn start - start prod environment

Additional Scripts

  1. type-check - run the type checking process
  2. format - run prettier for your current changes
  3. lint - run lint check

Coding style

  • Project has configured Prettier which helps stick to rules of coding style.
  • Check the shortcuts for your IDE to run Prettier for current file

Deployment

Every merge request which merged to Staging or Prod branches runs the deployment process to corresponding live environment