osync VS lerna

I tried googling and see this github repo for a shell tool called osync. Not sure if that's what it is or if that's a "red herring". From reading the description of that tool, it sounds like it's syncing files? With what? From what?

I still use it, because that's what I decided to set up after looking around and people raining praise onto it, but I wouldn't ever recommend it. It's a neat project, it does work if you essentially never touch it afterwards, but it's not a useful one as is if you do want to move things around a bit. I'd much rather use anything else, even proprietary solutions, than have to use Syncthing. When I stop lazing about and rebuild my system, I'm probably moving over to osync or something. Better that than Syncthing.

A tool called osync which might be able to do the job, it's like OS-level solution.

I've been considering simply moving over to osync because the little shit can't even handle a few additional files without crapping out. It works fine, when it works, but I almost don't dare touch it lest it crap itself out again. Its a sync program, adding a folder of some twenty pictures should not make it decide to dig an early grave.

Open the project up in your favorite IDE. Let's take a quick look at the project organization. The project has an Angular frontend and NestJS API backend housed in a Lerna monorepo. If you are curious about how to recreate the project, check out the repo's README file. I'll include all the npx commands, CLI commands, and the manual steps used to create the project.

Lerna currently maintained by Nx team

On Netlify's enterprise tier, approximately 46% of builds are monorepos, with the majority leveraging Nx and Lerna. Recognizing this trend, Netlify has focused on enhancing the setup and deployment experiences for monorepo projects. In particular they worked on an "automatic monorepo detection" feature. When you connect your project to GitHub, Netlify automatically detects if it's part of a monorepo, reads the relevant settings, and pre-configures your project. This eliminates the need for manual setup. This feature also extends to local development via the Netlify CLI.

This is the exact problem monorepos were born to solve. Not only will a monorepo let you share UI components, you'll be able to gradually add shared application logic as well (for instance, do all of your apps have their own logic for connecting to a database? you could roll that into a shared library with a monorepo). There are a lot of tools for accomplishing this in JS, but probably the most popular is lerna, which is built on top of NX (though lots of teams roll their own monorepo in nx without lerna, which IMO is a totally valid option).

To begin, you need to prepare your environment. A few ways to build a React package include tools like Bit, Storybook, Lerna, and TSDX. However, for this tutorial, you will use a zero-configuration bundler for tiny modules called Microbundle.

If so, are you using a monorepo tool like Nx or Lerna? If not, start there and see if it solves your problem.

I mean I don't know what your monorepo looks like, but for example infernojs (actually written with typescript) uses lerna, and lerna seems simpler than typescript references

Tools for publishing, such as Lerna (when using the --conventional-commit flag), follow this convention when incrementing package versions and generating changelog files.