Skip to content
This repository has been archived by the owner on May 28, 2019. It is now read-only.

Latest commit

 

History

History
110 lines (57 loc) · 3.59 KB

development.md

File metadata and controls

110 lines (57 loc) · 3.59 KB
Raw

Development guide

How it works

It consists of these main packages:

  • create-react-cdk

A CLI tool that runs CRA internally with --scripts-version cdk-scripts option

  • cdk-scripts

A custom CRA scripts that

  1. wraps original react-scripts,
  2. launch @storybook/cli,
  3. Apply specified custom template over default CRA generated project
  • cdk-template

Default react-cdk template. Provides some additional setting and overrides of original CRA template.

Usage:

  1. Install it globally via npm i -g create-react-cdk and run to create a project folder:

create-react-cdk <project-directory> [options]

  1. If you're using Yarn package manager, you don't need to install it before. Just use yarn create command:

yarn create react-cdk <project-directory> [options]

(it will always install the latest version)

  1. Or same with npx

npx create-react-cdk <project-directory> [options]

(add --ignore-existing flag to be sure you are using the latest version)

run yarn create-react-cdk --help in the root of project for CLI details

Keeping up-to-date

CRA internally always installs the latest version of scripts. So you don't need to update it each time after it becomes stable. Since we rely on CRA and react-scripts settings and use the @storybook/cli to add optimized for CRA Storybook configuration, we can focus only on react-cdk features.

How to generate projects locally

You can run scripts from .scripts folder. Each will generate a project in the ./test-gen folder.

  • test-cdk-scripts - via ./package/cdk-scripts

  • test-create-cdk - via ./package/create-react-cdk

A generated project keeps all dependencies in the own node_modules folder and can be checked out as a usual project

Note: you need to build tarball for cdk-scripts on each change (see How to build tarballs)

How to test with Jest:

run yarn test from root of project

It'll do the follow:

  • runs tests from ./__test__ folder

  • each test starts from running a script from ./scripts folder with the same name as a test file

  • These scripts generate a project into ./test-gen/scriptName folder. (scriptName - the name of script). This takes few minutes!

  • Then tests check the folder structure and test executing project scripts

At this moment there are two testing scripts:

  • test-cdk-scripts - to test ./package/cdk-scripts

  • test-create-cdk - to test ./package/create-react-cdk

How to run cdk-scripts commands

Though we can run these scripts directly from cdk-scripts folder, it has no sense since they are designed to work with generated projects. So we need to provide such environment for them:

cd test-script/launch-cdk-scripts

This folder simulates generated project but thanks to Yarn workspace linked to the ./packages/cdk-scripts. So you can edit ./packages/cdk-scripts files and execute them from this folder.

How to build tarballs

cd packages/cdk-scripts
yarn dev

This command will start nodemon to watch and build a tarball of this package on each change The tarball will be located in tarballs/cdk-scripts.**.tgz

We need to change file name for each build in order to use with CRA (we do automatically with packages/cdk-scripts/.dev/pack.js script)

How to debug

if you're using VSCode you can run scripts in the debug mode. For some of them there are tasks in configuration. Open DEBUG view on you left panel and select the script you want to launch. Open .vscode/launch.json to explore details and create other tasks.

Roadmap

See implemented and upcoming steps in the project Roadmap