1,314 karma · joined October 13, 2014
This is problematic given that this is how ESM is supposed to work.
We ended up bundling _all_ JavaScript to a single bundle and now Google indexes it with no problem.
Yarr is the only routing framework that was built from the ground up with the goal of enabling the render-as-you-fetch concurrent UI pattern. It allows code preloading and data preloading. This behavior is enabled even without opt-in to React's experimental Concurrent Mode.
Yarr was primarily architected by Eric Taylor, our super talented engineer, and it captures almost 2 years of our experience working with Relay and evolving render-as-you-fetch pattern. It's already in use in production at https://contra.com/
Days of closed-door marketplaces are over.
Feels exactly the same.
Use common sense
I work a lot with CLI programs, and I am often overwhelmed with the amount of logs that I need to comb through. The goal with this tool is to provide a zero-setup tool for analyzing logs.
As a user, you don't even need to create the account, you just generate a random room and start dumping the logs there using @roarr/cli (https://github.com/gajus/roarr-cli).
As an example, I made this room where I am just dumping random log messages every second.
However, most of the Snack complexity comes from orchestrating invitations. I've churned through couple hundred clients until we figured a mechanism to invite people to have these spontaneous events in a way that (a) is timed right (b) provides social validation. The current version has a growing number of active users and increase retention.
It is a fun weekend project that I use to learn about new technologies, measuring product usage and validating product ideas.
Do logs serve any purpose in application designed to utilize error tracking software such as Sentry, Rollbar, Bugsnag, etc.
Is there anything off the shelf that I could use today?
https://www.reddit.com/r/startups/comments/lqpjse/11_months_...