So excited about what we're working on atm. Basically 2024 was all about making Nx get more out of your way while still keeping the DX and power we love about Nx. And that's tougher than you might think. Tooling shouldn't go in your way; it should elevate your experience. - ThreadSky

juri.dev • 43 days ago

So excited about what we're working on atm. Basically 2024 was all about making Nx get more out of your way while still keeping the DX and power we love about Nx. And that's tougher than you might think.

Tooling shouldn't go in your way; it should elevate your experience.

Comments

juri.dev•43 days ago

Providing automations, better DX etc often requires more opinions, which pushes you away from how you'd set up things manually and what people might consider "standard".

Enterprises want more opinions, OSS wants more freedom and flexibility. Tradeoffs. But I think we're about to nail it.

juri.dev•43 days ago

This is a setup generated by Nx; actually you wouldn't even need to use Nx:
- npm / @pnpmjs / yarn / @bunjavascript workspaces
- best practices TS monorepo setup (TS proj refs synched automatically 🧙)
- directly leverages tooling (e.g. @vite_js CLI)

You almost don't see Nx, and yet it's there.

juri.dev•43 days ago

and the video 🤷‍♂️
https://bsky.app/profile/juri.dev/post/3lfsmkduats2i

lou.descioli.com•42 days ago

I'm having a bit of trouble following the latest best practice with Nx. If I have a traditional one-version Nx monorepo, with a single root package.json and a tsconfig.json & project.json for each lib & app, is that still optimal or is there a better way to do this now?

juri.dev•41 days ago

Hey. That's perfectly fine. And notice the single-version vs multiple version (package.json) setup is something apart from what I mentioned in the thread.

We're pushing out a bunch of content next week related to this, so I'll try to cover it. but tl;dr: it is still fine :)

juri.dev•41 days ago

We're probably going to lean more into the workspaces + TS proj references setup going forward, but will have content to support migrating people to it, if they want to. They don't have to, tough.

So nothing to worry about right now :)

lou.descioli.com•41 days ago

Does using workspaces imply a multiple package.json/multi-version setup?

juri.dev•41 days ago

It implies having a package.json / project (kinda like the project.json). It does NOT imply a multi-version setup necessarily and we still advocate against that. You could have that easier if you wanted to, though.
I'll prob have a dedicated video about that topic since it is a common confusion

lou.descioli.com•41 days ago

Hm, ok. So when adding a dependency to a project, you would still only add it to the root package.json, or you’d have to root and the project’s?

Comments

Posting Rules

Reply