lerna

:dragon: A tool for managing JavaScript projects with multiple packages. (by lerna)

Stats

Basic lerna repo stats
23
27,946
8.9
12 days ago

lerna/lerna is an open source project licensed under MIT License which is an OSI approved license.

Lerna Alternatives

Similar projects and alternatives to lerna

  • GitHub repo webpack

    A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.

  • GitHub repo pnpm

    Fast, disk space efficient package manager

  • GitHub repo nx

    Powerful, Extensible Dev Tools

  • GitHub repo ultra-runner

    🏃⛰ Ultra fast monorepo script runner and build tool

  • GitHub repo zx

    A tool for writing better scripts

  • GitHub repo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • GitHub repo Laravel 5

    A PHP framework for web artisans.

  • GitHub repo lodash

    A modern JavaScript utility library delivering modularity, performance, & extras.

  • GitHub repo prettier

    Prettier is an opinionated code formatter.

  • GitHub repo Babel (Formerly 6to5)

    🐠 Babel is a compiler for writing next generation JavaScript.

  • GitHub repo Symfony

    The Symfony PHP framework

  • GitHub repo husky

    Modern native Git hooks made easy 🐶 woof!

  • GitHub repo react-native-web

    React Native Components and APIs for the Web

  • GitHub repo Bazel

    a fast, scalable, multi-language and extensible build system

  • GitHub repo git-lfs

    Git extension for versioning large files

  • GitHub repo Buck

    A fast build system that encourages the creation of small, reusable modules over a variety of platforms and languages.

  • GitHub repo nixpkgs

    Nix Packages collection

  • GitHub repo io-ts

    Runtime type system for IO decoding/encoding

  • GitHub repo babel-sublime

    Syntax definitions for ES6 JavaScript with React JSX extensions.

  • GitHub repo next-firebase-testing

    Next.js + Firebase Testing Strategies

NOTE: The number of mentions on this list indicates mentions on common posts. Hence, a higher number means a better lerna alternative or higher similarity.

Posts

Posts where lerna has been mentioned. We have used some of these posts to build our list of alternatives and similar projects - the last one was on 2021-05-06.
  • A package for writing scripts on JavaScript instead of Bash
    monorepo is more like a "repo of repos". Like any tool or pattern, it has its is benefits and its drawbacks. Code sharing is one advantage. Another is centralized enforcement of patterns, practices and testing strategies. The downsides are pretty obvious. You end up with a lot of code in one place. There are a few of tools (eg Nx and Lerna) that make dealing with monorepos less painful.
  • I have a Node project inside another Node project. What should I keep in-mind in terms of organization/version control?
    Maybe check out lerna https://github.com/lerna/lerna
  • Announcing Rome Tools Inc, an open source first company
    I also forgot to mention the whole Lerna license debacle. https://github.com/lerna/lerna/pull/1616
  • Monorepo With Yarn Workspaces
    dev.to | 2021-04-14
    3.2. Lerna
  • A Next.js + Firebase TDD Environment Example
    dev.to | 2021-04-08
    Mono-repositories are a popular pattern, so I have implemented this approach with Lerna to show how the structure might look.
  • How do you import from "dist" directory of a Lerna package?
    reddit.com/r/node | 2021-04-08
    I use Lerna to manage a monorepo with several TypeScript projects. For those who don't know, Lerna creates symlinks between dependent projects and makes them see each other as normal npm packages. It's kinda awesome, but there is an issue. My project structure looks roughly like this:
  • How do developers get their UI to look exactly the same on mobile and inside the browser?
    But that's for newbies. The real solution is to put your shared components into a library, which is then imported by both your web app and mobile app. One way to manage all that is with the lerna package. Then all three libraries (web app, mobile app, shared components) would live in the same repo, and share dependencies and probably run the same test suites and CI processes.
  • How to Publish Component for Reuse
    reddit.com/r/react | 2021-04-01
    You could run your components as individual packages which other apps can consume - look at Lerna - https://lerna.js.org as a great solution to do this.
  • What is monorepo? (and should you use it)
    dev.to | 2021-03-31
    Lerna: monorepo manager for JavaScript. Integrates with popular frameworks like React, Angular, or Babel.
  • put multiple repos under one "repo"
    reddit.com/r/github | 2021-03-26
    Having a monorepo is also an option, you can use tools like lerna https://github.com/lerna/lerna
  • Node/React Monorepo - Help with reusing code
    reddit.com/r/webdev | 2021-03-25
    Hmm I think your problems could be solved here by using a private npm package for the server models, and lerna to handle the monorepo.
  • [Talk] Sharing Typescript Types between your Frontend and Backend
    I use lerna to manage multiple packages in each project (packages/client, packages/shared, packages/server). Each package has a package.json file.
  • Killblanks use pre-render and skeleton screen to solve page blanks
    dev.to | 2021-03-08
    Currently Killblanks is built on lerna and consists of three core functions
  • JavaScript Monorepo Tooling
    dev.to | 2021-02-13
    🐉 lerna
  • Typing front end form bodies
    I usually create 3 packages for a typical app: client, shared, server. The shared package includes interfaces/types/utilities that can be used from either the front or backend. You can put all 3 packages in 1 repo (I've been really enjoying Lerna and Yarn workspaces for managing monorepos).