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

@wishwork/create-wish-work-app

v1.9.0

Published

CLI to Bootstrap Wish Work Products

Downloads

9

Readme

Create Wish Work App

npm version
This CLI ships with the main React and Storybook configuration files you'll need to get up and running fast. There are standards for front-end development that has been initialized by Wish Work team for products which is developed by freelancers and developers. In this README, we provide useful information so that developers understand the project structure.

If you have questions or need help, please ask in GitHub Discussions.

Motivation

As we grew as a team for development of many platforms, we struggle to define a compelling structure so that anyone could easily understand the products which has been developed by Wish Work team. For instance, one may use json-server for local development and one may not, one may provide local environment in specific manner which contradicts with other, and it may cause overwhelming problems for understand the project, where is redux files, where is assets, to name but a few. As we believe in Convention over Configuration for better development, we provide our solution for establishing the first architecture of the project and developers just focus on the development problems that should be solved.

Installation

First of all open the terminal and write below command:

mkdir my-wish-app && cd my-wish-app

and then:

npx @wishwork/create-wish-work-app

After that the project will be initialize. there will be some questions that you should answer.
For example which template would you prefer Javascript or Typescript.

Structure

The project structure will be as below:

.
├── .storybook             # Storybook configuration
├── .github                # Github workflow configuration
├── src                    # Source files and folders
├── test                   # Automated tests (alternatively `spec` or `tests`)
├── Makefile               # Makefile for running commands (e.g. make local)
├── index.js               # Main file for running the main app
├── Environment.js         # Javascript environment for using from process.env and return an object for better usage. 
├── .env.local             # Local env (activate by `make local`)
├── .env.development       # Development env (activate by `make dev`)
├── .env.production        # Production env (activation by `make production`)
├── LICENSE                 
└── README.md   

Inside a src folder would be some other folders as below:

src
├── App.js                 # 
├── components             # Reusable components
├── stories                # Stories for getting preview
├── common                 
     ├── assets            #  assets like images, identity.css, etc
     ├── mock-api          #  consists of two json file one named mock.json (json returner) one named routes.json (route handler) 
     ├── utilities   

Local Server

For running json-server for local development, use below command:

make json-server

For more information about json-server library please click here.

Environment Variables

As mentioned above, there will be three envrionment variables: .env.local , .env.development and .env.production.

Each of them has it's own usage.

For local development you could use below command in the root of the project and also use .env.local:

make local

For staging development you could use below command in the root of the project and also use .env.development:

make dev

For production you could use below command in the root of the project and also use .env.production:

make production

Storybook Preview

you could use below command for getting preview from the storybook.

make storybook

This storybook is based on Wish Work Design System.

Auto Deploy on Github.io

There is a workflow for better testing of the application for deployment. For this purpose we provide a main.yaml file in .github/workflow folder. you should create two instance in your repository settings:

  1. ACTIONS_DEPLOY_ACCESS_TOKEN
  2. REACT_APP_GITHUB_URL



Make sure GitHub Pages option in your GitHub project settings is set to use the gh-pages branch.

For more information: Setting up a CI/CD workflow on GitHub Actions for a React App