23 Matching Annotations
  1. Jun 2021
    1. These days, Monorepo’s and Typescript are very popular, but configuring the development environment to work with both is still a fairly complex task.
    1. Monorepo use cases
    2. Apart from that it’s just more convenient to have all your source files opened in a single IDE instance. You can jump from project to project without switching windows on your desktop.
  2. May 2021
    1. New changes to the old repositories can be imported into the monorepo and merged in. For example, in the above example, say repository one had a branch my_branch which continued to be developed after the migration. To pull those changes in:
  3. Apr 2021
  4. Mar 2021
  5. Oct 2020
    1. I chose to use a monorepo: to reduce development friction in managing my various projects to utilize patterns across my projects
    1. Wouldn't it make more sense contextually to put this in the Sapper docs site; https://sapper.svelte.dev? We could also have a repo for the more complex examples but then it would need to be maintained etc.
  6. Sep 2020
    1. For a non-monorepo package you can simply point directly to the Github repo. This case is similar, but you want to scope it just to a single package within the repo. For those that make monorepos they don't necessarily need this feature. It's for those that use projects that use monorepos. Telling them to not organize their projects into monorepos doesn't help people who make use of these projects.
    2. npm's inability to handle monorepos then i'd have designed my repos accordingly
  7. Apr 2020
    1. You'll also have a directory structure that looks like this:

      Not a monorepo. Individual repo for each gem. I wonder why not a monorepo.

  8. Nov 2019
    1. uses a "monorepo" organization style for managing multiple npm packages in a single git repo. This is done through a Yarn feature called workspaces.