Why you should be using NX.dev

So why NX?

  • Workspace management — to manage the projects in your repo
  • A plugin system — to extend NX with your own project templates/runners
  • E2E testing tools for your plugins — high level APIs to write tests against a temporary workspace create for your test
  • Affected build calculation (only build what has changed)
  • A VSCode extension to surface plugins and their options

Further thoughts

  • PNPM as my package manager
  • Changesets to version and publish my NPM packages
  • TypeScript project references to keep type checking fast
  • TSUP to package my NPM packages before publish
  • Pulumi to deploy my applications

--

--

--

Co-Founder featureboard.app | Principal Consultant arkahna.io | Previously Tech Lead Seven West Media WA | International Speaker | OSS | Mentor

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

The Rise of JAMstack 🚀

Announcing the Euler SDK

Conditional Rendering in React With Examples

React Code.

Velo by Wix: The utils for repeated item scope event handlers

You Need to Write Effective Unit Tests

Make web real-time with GraphQL subscriptions

React Resources:

How to Link Files in Node.JS Using Require

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Jake Ginnivan

Jake Ginnivan

Co-Founder featureboard.app | Principal Consultant arkahna.io | Previously Tech Lead Seven West Media WA | International Speaker | OSS | Mentor

More from Medium

Svelte.js and the History of the Internet

🤔 Estimation Chaos in a Full Stack World 🌍 (FSW)

Migrating large codebase to TypeScript. Do it right from the beginning.

Epic Patterns of RxJS and Redux-Observable