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

@osynlig/support-tool

v0.3.2

Published

The Osynlig Support Tool

Downloads

490

Readme

🧀 The Osynlig Support Tool

Getting started

  1. Install into project with npm i -D @osynlig/support-tool.
  2. Add "ost": "ost" to scripts in package.json.
  3. Run npm run ost init to create example template in .ost config folder.
  4. Add variables to the .env file in your project root, see .ost/.env.example for available variables
  5. 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

  1. Run npm run ost tokens
  2. 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

  1. Clone the repo
  2. Run npm install to install dependencies
  3. Run npm run start and keep it running in a terminal

Test scripts

  1. Create a script in src/commands/
  2. Import your script in src/index.ts and add it to the program
  3. Run cd testdir to go to the test project
  4. Run npm install to install dependencies for the test project
  5. 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?