Serious problem with documentation
See original GitHub issueI still don’t understand how to get even the basic hello world set up with Twind could find myself give up this project.
What is the next step I’m suppose to run after:
npm i twind
and documentations guide is confusing despite with years of programming experience in other area.
Issue Analytics
- State:
- Created a year ago
- Comments:7
Top Results From Across the Web
Poor Documentation: Why It Happens and How to Fix It
In general, Stewart says poor documentation is defined as that which is lacking clarity, specificity, or completeness, and is of overall poor quality....
Read more >11+ Critical Document Management Challenges and Solutions
Document management challenges can affect a host of concerns. Digital file management chaos, high document process cycle time, document ...
Read more >Top five product documentation challenges Canvas Envision
The five biggest challenges to product documentation are Quantity, Creation, Quality, Consumption, and Obsolescence. Learn more.
Read more >Nursing documentation: How to avoid the most common ...
Top 9 types of medical documentation errors · Sloppy or illegible handwriting · Failure to date, time, and sign a medical entry ·...
Read more >6 Problems Caused by Inefficient Document Management
4.) Problem: Manual processes have outdated or no security measures - filing cabinets are rapidly becoming outdated. Solution: Your documents ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Tailwind v3 is only supported in the twind v1 beta (https://github.com/tw-in-js/twind/tree/next).
@bstro If you are calling/using
twin your components module on the top-level then these will run beforesetupin your main entry has run. I typically put the setup code into an extra file likesetup.env.ts:And then in your main/app file import that file before your components:
I hope this helps.