@osynlig/support-tool
v0.3.2
Published
The Osynlig Support Tool
Downloads
490
Keywords
Readme
🧀 The Osynlig Support Tool
Getting started
- Install into project with
npm i -D @osynlig/support-tool
. - Add
"ost": "ost"
to scripts in package.json. - Run
npm run ost init
to create example template in .ost config folder. - Add variables to the .env file in your project root, see .ost/.env.example for available variables
- Run
cp .ost/config.example.json .ost/config.json
to copy config file
Usage
Scaffolding templates
Commands
Run npm run ost make component [ComponentName]
to create a new component from a template.
Configure template types and target directories .ost/config.json.
Generating icons from Figma
instructions missing :(
Generating css files containing tokens from Osynlig Baseline Tokens
- Run
npm run ost tokens
- Token css files will be generated to target directory specified in config.json
External libraries
- Commander for CLI-functionality
- Ora for terminal spinners
- figma-js as wrapper for Figma API
- ejs for population of templates
Developing
Setup
- Clone the repo
- Run
npm install
to install dependencies - Run
npm run start
and keep it running in a terminal
Test scripts
- Create a script in
src/commands/
- Import your script in
src/index.ts
and add it to the program - Run
cd testdir
to go to the test project - Run
npm install
to install dependencies for the test project - Run
npm run ost [your-script]
to test your script
Todo
- [ ] Warn when trying to create component that already exists
- [ ] Config for src dir
- [x] Make sure created component ends up in the right dir
- [x] Make sure we are in an initialized project
- [x] Typescript
- [x] ESlint
- [x] Prettier
- [ ] Tests
- [x] Make into installable package
- [x] ost init to create example template structure
- [x] Create readme
Maybe?
- command to create a prettier config?
- command to create a readme base?
- fig/autocomplete helper?