recursive-proxy-mock VS nx

Let's take a specific example. One of my libraries recursive-proxy-mock is bundled with Rollup. If you take a look at dist/cjs/index.js you can see there is one big file with everything in it, all bundled together. There are named exports for each thing. This can easily have unused code eliminated either via tree shaking or dead code elimination. I've never made a distinction as to which applies in which scenario since both should always be used together. But I guess my point is, a bundled library doesn't need to have any special format which would require a bundlers help to drop dead code.

If you want to check out my build config for my library that sounds very similar in architecture to yours, feel free: https://github.com/CreativeTechGuy/recursive-proxy-mock

Take a look at the recursive-proxy-mock library. The ability to create an object where every property or function "exists" with infinite depth is a really powerful primitive. Not just for providing mock implementations to complex objects for testing, but also for the ability to store and replay operations on another object in the future.

If you are just looking for a TS library config (not related to react) then here's a good example I can share: https://github.com/CreativeTechGuy/recursive-proxy-mock/blob/main/rollup.config.js

One notable feature is the ability to remember selected tabs. When you select a specific tab on a page, all other tabs on the page with the same name will also be selected. This selection will persist during your next visit to nx.dev.

Hono does have a template application for Vercel, but in my case, my requirements were different (aren't they always 😅). I was working in a monorepo (using nx) because I wanted to manage my libs, tests, and examples all together in a single place, instead of having different repos.

Recently, My coworker is using Nx to automate his workflow, including automated release using semantic version. I found this method quite useful, so I want to re-implement on single GitHub repositories (without Nx).

I started a discussion on GitHub concerning that subject: Design Nx Plugin Project Crystal

Nx

We are looking for companies to partner with on the Analog project to support development of the project. Thanks to Snyder Technologies for being an early adopter and promoter of Analog, Nx for joining us as a sponsor, House of Angular, and many other backers of the project.

Additionally, thank you to all our community launch partners across the frontend ecosystem for helping us bring Storybook 8 to the world! Thanks to Chromatic, Figma, ViteConf, Omlet, DivRiots, story.to.design, StackBlitz, UXpin, Nx, Mock Service Worker, Anima, Zeplin, zeroheight, kickstartDS, and Kendo UI.

The advent of esbuild, the native support for ES Modules in browsers, the widespread adoption of import map, the emergence of tools like Native Federation, and the Nx ecosystem all combine to forge a flexible and well-maintained Micro Frontend Architecture.