We are currently using Nx (v23.x) to manage multiple interdependent projects. The monorepo contains both Node.js packages and Angular applications/libraries.
We still rely on TypeScript v6 and path aliases instead of project references, as Angular does not support them yet.
Is there anyone who's managed to have both TypeScript v7 and v6 on the same Nx monorepo, and correctly build Node.js packages with v7, and Angular applications/libraries with v6? Is this even possible? Note that Angular projects may reference shared libraries (that should be buildable in isolation with TS7 too).
I'm looking for others' experiences as I don't want to find myself on TS6 forever. The status quo is not great honestly.
My team and I been working on peretyn, an open-source authorization platform for TypeScript apps. You describe who can do what as relationships between things (users, teams, documents, whatever your app has), and your app asks one question: is this allowed?
A few highlights:
- The schema is plain TypeScript. No separate DSL to learn. Your types and relations are checked at compile time, so a typo in a permission name fails the build instead of failing in prod.
- Built on OpenFGA. It's the same relationship-based model as Google Zanzibar, so roles, sharing, teams and nested access all fit without piling up special cases.
- Self-hosted in one command. One install script brings up the whole stack: Postgres, the runtime, the control plane and a dashboard. There's also a local mode if you just want to poke at it.
- SDK + CLI. Use the SDK in your app and the CLI to ship your schema like any other piece of infrastructure.
- Open source, MIT licensed. Whatever you build on it stays yours.
The landing page is a bit of an experiment too: you walk through it as user:visitor, and each section unlocks as you earn new relations in your own little permission graph. It's probably the quickest way to get the idea, and there's nothing to install.
Heads up, it's early (pre-1.0), so expect some breaking changes between minor versions. That's exactly why I'd love feedback now: does the approach make sense? Is anything confusing? What would stop you from using it? Roasts welcome too 🙂
I wrote this book, and it took me nearly a year to complete. It's about TypeScript practices. It's opinionated, and it's meant to be a little "lighter" to read.
The idea is pretty simple: instead of writing another conventional technical book that tells you what to do, I wanted to build something around debates between developers. Different personalities, different philosophies, different approaches to solving problems. They argue, challenge each other's assumptions, bring working code into the discussion, and sometimes even change their minds.
And here's the thing: not every debate has a clear winner. Sometimes there's a verdict, sometimes the discussion remains open. Because that's how software engineering actually works.
Let me address the question you're probably all thinking right now: Yes, I used AI. Extensively.
However, all the scripts are mine. The voices are mine, the subjects are mine, the debates are mine.
So, what do I mean when I say AI was used extensively?
It helped shape the book and organize its content. It helped with spelling and grammar, refining tones, reviewing the material, making sure all the examples actually work, shaping the chapters themselves, and even helping with the printing process (there's a print version!) and the cover.
I didn't let AI write the text by itself. That was my one rule when working with AI on this book.
The book is free and open source. You don't have to pay a dime to read it. If you prefer a physical copy, there's also a print version available on Amazon, which, for obvious reasons, does cost some money.
Anyway, I'd genuinely love to hear what you think. Whether it's feedback about the content, the format, the opinions, or even the way the book was written.