pyqant

Generates a static React project with esbuild, TypeScript, and styled-components.

Exact structure of the generated project is not guaranteed. Semantic versioning does not strictly reflect the "compatibility" of one version of generated project to the next. But changes to project templates will always increment the version number, typically a patch. In general, I'm not one to change my mind quickly on trends, so the overall shape of the generated project should remain largely the same[1]. Most of the churn will likely be from keeping up with vulnerabilities and adjusting the starting template code as libraries come and go.

I'll do my best to make sure changes to the CLI follow semantic versioning. New flags and deprecation warnings will arrive on minor versions. Backwards incompatible changes will arrive on major versions.

Installation

npm install -g pyqant

Usage

pyqant my-project

Options

--author <name>       Author for package.json (default: git config user.name)
--node-version <ver>  Node version for .nvmrc (default: current LTS)
--no-eslint           Skip ESLint setup
--no-git              Skip git init
--skip-install        Skip npm install after scaffolding
-d, --directory       Create custom directory (default: proces.cwd()/<projectname>)
-v, --version         Show version number
-h, --help            Show help message

Development

# Install dependencies
npm install

# Test locally
node bin/cli.js my-test-project --skip-install

# Check what would be published
npm run publish:dry

Publishing a new version

Note, that while the npm website is lax when it comes to logging in with a VPN, the publishing endpoint will hang on the authentication loop when trying to publish from behind a VPN.

[1]: This project is a continuation of https://github.com/worc/static-react from 2019