I use tailwind. I like tailwind. But I'm still not sold that this is better than vanilla CSS, CSS-in-JS, or other alternatives.
If anything, it's even more confusing sometimes.
I constantly see tweets about how complicated TypeScript in a monorepo is, so I've been writing a pretty in-depth article about it. Expect it in the next few days!
Looking to integrate
@typescript
in a monorepo? Are you overloaded, confused? I've been there...
As such, I've conjured all my experience and knowledge on this subject to provide an in-depth guide for using TS project references. I hope it helps!
It's been an amazing 2.5 years at
@coinbase
working with first-class team mates on design systems, dev tooling, and react native, but it's time to move on.
I'll have some big announcements in the coming weeks!
After many weeks of conversations and interviews, I can excitedly announce that I will be joining the
@coinbase
team next month! Really stoked to work on such a high quality product.
Are you unhappy with the Node/npm ecosystem? Hoping for something better? Me too.
Say hello to espresso ☕️, an in-development next-generation package registry/manager.
🟧 ESM only, no CJS
🟫 Builds packages on demand
⬛️ ES build targets
Learn more:
Played with
@solid_js
on stream for the first time. Initial thoughts:
- Lack of Storybook type environment makes it hard to experiment at first. Threw up a quick Vite app to move forward.
- Ecosystem felt rough until I stumbled upon solid-primitives/aria.
I hear that build systems are all the rage lately, so I'm happy to announce moon! A build system written in Rust, designed to scale for companies and projects of any size!
I have a long list of cool things planned, so stick around!
Do you use
@adonisframework
? Do you wish it generated types for models and controllers? Great, me too, so I wrote a codegen provider that does just that! Will do more testing and then release it.
After a year and a half of development, moon has finally reached a v1 🎉! The next year will be very exciting.
🗜️ Project constraints/boundaries
🏷️ Project tagging
🐚 Shell wrapping for system tasks
🗝️ Env var substitution
🔩 New token variables
CI costs for
@tothemoonrepo
was costing me about $700 a month, which is absurd. So instead, I converted an old unused macbook and an $800 windows laptop into self-hosted runners.
Now my CI costs are basically zero, and these self-hosted runners are beefier than what GH provides.
Everyone's focusing on linters/formatters in Rust, but I really want a typechecker written in Rust. TypeScript is great but it has so much baggage at this point, and the perf is bad.
This past year has been wild. During the entirety of the pandemic, I...
- Was let go from Airbnb
- Joined Coinbase (and helped launch React Native)
- Got in a relationship
- Got engaged
- Bought a house
- Uncle to my first niece
- Major progress on open source
What's next?
@nickemccurdy
@jaydanurwin
You need to handle `credentials`. And using fetch().json() forces you to do that everytime. I can build my own abstractions/wrappers, and at that point, might as well just use a lib.
@mehulsharmamat
It's just a lot to understand when going back to old components and trying to figure out wtf is going on.
CSS is much more organized as everything is read top down.
My setup-rust action now caches `~/.cargo` and `target`. Brought CI times down upwards of 90%!
For example, lint on windows before was 5m, after is 45s!!!
Ive been able to gather my thoughts these last few days, and I just want to thank everyone for their support, especially Airbnb colleagues. It's heartwarming to know I left an impact and will be missed, even from individuals I never met!
If you write React
@typescriptlang
and want to generate PropTypes from your interfaces, I just released an alpha of my new Babel 7 plugin! Would love some testing and feedback.
Why does no registry (npm, crates, etc) include a changelog on the package page??? It's such a hassle having to find the repo, then find the changelog.
This is so weird to me. Why prettier? The tool that is the fastest and least problematic in the JS ecosystem???
Why not a better linter? Test runner?? Type checker???
I have ideas for:
- An alternative npm package/registry spec, that would help to alleviate all the problems the ecosystem currently has.
- A new CSS/styling approach that is not CSS-in-JS or Tailwind.
I wish I had more time to really prototype these 😅
Thoughts in TS return inference: Use it sometimes, but not always.
For primitives, complex types, and const/literals, it works great.
But sometimes the inf types are too broad, and returning an explicit type that narrows it is sometimes better.
TLDR; both approaches are fine!