Comments (8)
I bet that's nice. However, in this particular case, it makes more sense to implement a .card
as a class, rather than a component. That's just one example. The one from Tailwind docs is another. btn-primary
isn't always going to be used in an actual button, it can alse be a link.
I don't think it's smart to make a component that does two things -> two components -> when our btn-primary changes, it has to be changed in two places if we don't use @apply for it. So we're going to use @apply for it 😸
I guess anyone who was able to get the stack running in the first place can also figure out how to add a CSS file so I'll accept "my defeat".
Closing.
from blues-stack.
@k1sul1 Problem is not related to missing input file, as Tailwind has a default input file with the following content
@tailwind base; @tailwind components; @tailwind utilities;Tailwind is also properly installed, so I guess there should be some other problem on your end.
I can confirm that @MichaelDeBoey was right. I have just finished doing a page with Tailwind UI and everything works without configuration changes.
I hope your issue is resolved @k1sul1. If it's not, please make sure you have installed the dependencies stated here: https://tailwindui.com/documentation#react-installing-dependencies 🤞
from blues-stack.
Yeah, that was my first thought, not installing Tailwind UI properly, but that wasn't the case. The component that I added doesn't require those dependencies. I've gotten pretty far in the project without having any issues after the initial one.
from blues-stack.
@k1sul1 Problem is not related to missing input file, as Tailwind has a default input file with the following content
@tailwind base;
@tailwind components;
@tailwind utilities;
Tailwind is also properly installed, so I guess there should be some other problem on your end.
from blues-stack.
Thanks for disproving my hypothesis / guess. Could've been a classical case of needing to run "npm install" again.
It was very weird, because SOME things from Tailwind worked, like the default frontpage looked like it should've, as did the login form. Only the thing that I added didn't work.
Nevertheless, I think it would make sense to include the input file manually, because let's be real, you're going to want to write at least some CSS despite using Tailwind. I went in an edited app/styles/tailwind.css directly before realising I was in the wrong file.
from blues-stack.
let's be real, you're going to want to write at least some CSS despite using Tailwind
Tbh, I never write custom CSS anymore.
And now that Tailwind supports arbitrary values, it's even less needed to write custom classes.
Tailwind also is encouraging the use of components instead of classes, so I think we're fine with not having the file by default.
from blues-stack.
In my case current tailwind setup inside blues stack cannot translate the responsive class at all.
from blues-stack.
@trungthecelestial please open a new issue if you're having a problem, and provide more details and a reproduce case.
Commenting on an 6 months old & closed issue won't help us help you!
from blues-stack.
Related Issues (20)
- New Defer API does not work with blues-stack HOT 11
- When Using Express Adapter Throwing Responses will break the app HOT 1
- great repro
- Race condition in npm run dev HOT 5
- Base Repo OOMs on Fly.io HOT 7
- Fly.io -> Error: Can't reach database server HOT 7
- `npm run typecheck` fails on fresh project HOT 7
- blues-stack 2.0.0-pre.5 - LiveReload is not working HOT 2
- v2_dev leaves one node process behind after shutdown HOT 1
- Scripts variant in README to support the Yarn inclined HOT 1
- Deployment issue. Node version >18 needed
- Update server.ts to watch version.txt
- Error when trying to run the docker image HOT 3
- Latest server.js code breaks HDR HOT 1
- Some URLs in the `/build` path were 404 not found after making changes in development mode HOT 1
- Vite support
- Build failed while running npm run build on blues stack HOT 2
- Install an esm package dependency
- Error Code 134 on Deploy of Base Repo HOT 5
- OOM error in deploy requires NODE_OPTIONS space size to be increased/defined HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from blues-stack.