@jorgebucaran
We just have to all remember how you copied colorette from kleur. Seem everyone in the ansi space all copying from each other. Just congratulate nanocolors — spotting a perf boost where no one else did. Took the best of all worlds.
@ryanflorence
fetch(`/graphql`, { body: JSON.stringyify({ query: '{ some { thing } }' })
slightly more characters, but other than that you can be on your way
@jarredsumner
you've got a laundry list of bugs building up man, I don't want to tell you what to do, so take this as friendly advice. But if i was in you, but as me; id focus on stability and reliability as a priority now.
you can always make things faster, we respect you for that. but
"If you try to build something for reuse, without ever having *had* multiple uses, then the thing you're building probably gunna suck—or at least need to change a bunch of times soon after releasing"
-
@lukeed05
Want to see the latest from the GraphQL js server community, here's a sample implementation complete with defer, stream and live directives.
- graphql-helix
@ReardenQL
✅
- sse-z
@ReardenQL
✅
- meros
@slightlycode
✅
- graphql-live-query
@n1rual
✅
@fat
@vercel
meanwhile as the children play around with
@vercel
,
@CloudflareDev
busy building an infinitely better Vercel. Maybe time we rebuild Jira, probably more applicable!
@lrvick
@github
@dmca
It's not that bad. Sure you can push commits. But you can't push refs. So master will always be theirs. And those commits aren't discoverable.
However, this is a great way to share pirated stuff! Push your commit to a public repo, and share the link. And boom click the download
I think folk are not realizing the freaking awesome thing that this is!! 🎉🚀
`worktop/cookie` — 606B
`worktop/jwt` — 1KB
`worktop/buffer` — 1KB
Most can be used in any target, node,browser,worker.
All small, all fast, all 100% w/o bullshit.
`npm add worktop
@next
` today!🍻
I've been experimenting with `worktop
@next
` lately (already available) and here are some of the recent additions:
🔀 New `buffer` module, which contains many encode/decode utils, including a `buffer.from` helper!
🔐 New `jwt` module with many signing functions ready to go
An up and coming pattern for Relay. The entrypoint! In this diagram, you can see I'm rendering-as-I-fetch per route. But entrypoints can be at any level. Rule of thumb, anytime you code-split with data requirements, you entrypoint it.
I'm at a pretty low point in my life at the moment, and for those of you that have shown me a great deal of support! Thank you! 💞
It's a consistent reminder to be kind to yourself. The world may be against you, but YOU don't have to be. 🍻
The problem I have with live coding tests is that it sets and unrealistic representation of one's capabilities. I personally shut down when I'm nervous, not about stress or anything. Maybe product of lack of confidence?
@jarredsumner
yo actually, dude ship this! but call it jobs — and make it super simple to spin one-off, offs!
bun:jobs
#queue
(MyJob, params)
mimicking the `setTimeout` api
@mjackson
just different — discord is for open communities, and slack is for closed. How many corps do you know that use Discord as their company communications medium?
Hot off the press `storybook-addon-grid`~! 🖼
Gets you a Figma inspired column grid for your stories.
`yarn add -D storybook-addon-grid`
Go give it a try, let me know what you think!
@MarzBarGaming
No no no... PayPal didn't get hacked. *Your* PayPal got hacked. Unless I'm horribly mistaken, but I have not seen a single breach post since February.
To my graphql friends,
type Thing { id: ID! } — is that locally unique
type Thing implements Node { id: ID! } — is that globally unique
As to say, you can have ID scalars which aren't globally unique, but when implementing Node MUST be globally unique?
> mainly about relay
Finally able to share what I've been doing for the past few months. We've been building the ability to restrict which files form part of prompting in IDE.
I'm so keen to hear your feedback!
@adamwathan
is that bad? how else do you say seamless way?
plagiarism in an MIT world is hard to justify my friend. I've had
@apollographql
copy my stuff and claim it's theirs.
complaining just makes you look silly 🥴
@jarredsumner
doesn't the spec specifically not specify this, meaning it's up to the server to decide how strict it wants to be?
or is this exactly why you're asking 😅
I'm fully convinced working with designers than can also code is a where true magic happens. ✨
Guess that's what's really nice working for a developer platform!
@_jxom
a while ago
@theKashey
showed me that caching thousands of tiny files is slower than caching a single big file. so pre-tar your node_modules, and then cache it.
lz4 -d /tmp/pnpm_store | tar -xf - -C $(pnpm store path);
tar -cf - . | lz4 > /tmp/pnpm_store
Server-Timings is quite cool for your monitoring, plugs right into the `performance` tooling. Interesting stuff this;
Streaming react w/ timings:
(notice the Server Timings)
👋🏻 to my Workers KV friends, want to cache arbitrary function results into KV, think like a stale-while-revalidate but for _anything_.
I got you covered 👉
@dhh
think we've proven already that although import maps, and esm made it possible.
you still want to keep network traffic minimal, and bundles are still important