nodejs / nodejs/doc-kit

[yay/nay] Tailwind?

Open
#1,016 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
64
Forks
71
Avg merge
2d 17h
Merged PRs (30d)
31

Description

Since we publish this repository, we can technically enable Tailwind using a pipeline like:

  1. If development -> Load Tailwind plugin into Vite
  2. On publish -> Convert TW CSS to regular CSS

The caveat here is that it'll make development builds slower, as it needs to load and process Tailwind.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the repository's current development and publish pipeline, then assess how a Vite Tailwind plugin would fit development and how Tailwind CSS would be converted during publishing. Done means a decided approach that addresses the development-build performance trade-off and specifies the required pipeline changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, tailwindcss, vite
Domain
build-system, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.