razzle
razzle copied to clipboard
jaredpalmer
Looking for help / maintainers (Please read)
It seems like there has been very low traction on this project @jaredpalmer
cc @maintainers-of-razzle (woops, pinged maintainers by accident)
There are many PRs with no comments from any of the maintainers, is there anything we can do to get this project back up and running?
EDIT: I will start working on the PRs from oldest. If there is anything that is super urgent please just @ me to that PR / Issue and I will try to get to it in a timely manner
No answer yet. Anyone up for forking to “dazzle” if another week goes by?
I’m not actively working on Razzle at the moment. It’s not that I’ve moved onto other alternatives, it’s just that I’m not currently working on any SSR applications. It is thus a lower-priority project for me until 1) React’s new server renderer comes out and 2) webpack 5 drops. If folks want to step up and help out that would be rad. If you’re interested, send me a DM on Twitter.
React is getting a new server renderer? Where can I find out more about this?
well @jaredpalmer is not responding on twitter or on github sooo we are just stuck here in limbo
Razzle is good, SSR in mind is good, wish this project can go on. One day I need to mix gatsby and CRA, I found no better choice than Razzle.
Alrighty folks, Im gonna start working on the PRs from oldest. If there is anything that is super urgent please just @ me to that PR / Issue
I don't use SSR to run in production. I use SSR with Razzle to produce static pages :). Razzle is no magic to me, it's good so far. I'm happy to hear the project is going on.
@elliottjro How about a new release that at least includes 08092dc to get rid of this audit advisory warning in razzle 3.0.0? https://www.npmjs.com/advisories/786
@jaredpalmer please add me to contributors so I can start closing some of the issues.
It would also help with managing issues by automatically closing stale ones. Just need to change one line in the stalebot config.
@elliottjro hello, would you mind to update CONTRIBUTING.md file? it's little confusing that we have a master and next branch and people just opening pull requests on the master branch ...
I think having master, develop and canary branches is very useful, we could also add automatic releases for canary branch ...
I'd be happy to help as well @jaredpalmer - I actually deprecated my cra-ssr boilerplate project in favor of suggesting people use Razzle. I'm a full-time OSS contributor and would be happy to merge some PR's and get this project running again. @elliottjro would you like some help?
@jaredpalmer sent you a message on twitter. I would also be happy to contribute.
me (@nimaa77) and @fivethreeo are working on this project.
if anyone is reading this and wants to participate just create a Pull Request and that's all
Fyi, been in hospital 1 and a half week. This project nearly ended abruptly, may abandon it due to health.
I'm so sorry to hear that! Will you be okay? Is there anything we can do to help you out?
Luckily I live in Norway with free healthcare and have a caring family, feeling better now but may need a drastic lifestyle change. Well wishes will do plenty :) Wrt razzle there is https://github.com/jaredpalmer/razzle/issues/1852 , I can lead razzle but if no one helps with design decisions, coding and docs razzle is sadly no more.
Hi! How can I help you maintaining this project? I think razzle is awesome, and I choose it again and again over Remix or Nextjs.
Thank you, for your work!
@sergeysova I was one of user of razzle. In general it's versatile enough for some kinds of web apps, but not all. For most of use cases, my suggestion is just use Next.JS. Some lackings from razzle from my experiences:
- Static site delivery: Lacks of toolings like getStaticProps, or incremental static site building
- Lack of 3rd party adoption: For most of startup, it's a real deal if 3rd party service have an example on the integration with your framework.
- Separation of API and Frontend: It's good to separate those things.
@revskill10 I wanna use state managers to manage business-logic and all of the application behaviour. Nextjs is trying to steal control over the things. For example, I want to redirect user only from the business-logic (my model). But I need to use Nextjs-hooks instead, and nail my model to a React-component. It's awful
Hi! How can I help you maintaining this project? I think razzle is awesome, and I choose it again and again over Remix or Nextjs.
Thank you, for your work!
Me too, just use razzle, not nextjs or remix. The development experience of razzle is better, you can control everything.
