19 ms·
I have been a tad skeptical about how Blitz.js would accomplish "batteries-included" elegantly, but 5 min into reading the (very thorough) docs and it seems lik
by cwackerfuss 6y ago
I have been a tad skeptical about how Blitz.js would accomplish "batteries-included" elegantly, but 5 min into reading the (very thorough) docs and it seems like a fantastic amount of abstraction to work with. You're a genius flybayer!
2 questions:
1. How the docs read right now, I'm cautious about the "recipes" concept. It's not clear why I'd need to use a recipe to install Tailwind instead of installing Tailwind via NPM. I'd love the docs to explain what "coupling," if any, occurs with Blitz <> a recipe's dependencies, so I can better understand what I'm opting into by choosing the framework.
2. Is there a roadmap for API-only implementation, like Rails? If I want to use some of my Blitz endpoints from another client is that possible?
Thanks!
- flybayer 6y agoHa, thank you! > Re: recipes You don't have to use recipes. Recipes simply package a number of manual steps into a single automated command. Recipes let you install a library without looking up the install docs. Recipes are roughly "install dependencies + codemods". So for example the `chakra-ui` recipe installs the needed dependencies and adds the theme provider to your app root. There's currently zero coupling with recipes. The end result is exactly the same as if you did everything manually. > Re: API-only Currently you can do that. You can use the API routes (which give you direct access to Node req, res objects. And don't add any pages (or just a few, as you want).
- cwackerfuss 6y agoSweeet. I could actually see Blitz being really useful as an admin interface over an API, where the generated API drives web/mobile apps.