Need advice about which tool to choose?Ask the StackShare community!

Lerna

929
137
+ 1
0
Webpack

40.7K
27.5K
+ 1
752
Add tool

Lerna vs Webpack: What are the differences?

Key Differences between Lerna and Webpack

1. Installation and Usage: Lerna is a tool that helps with managing multiple JavaScript packages in a mono-repository, while Webpack is a module bundler primarily used for bundling JavaScript files. 2. Purpose: Lerna focuses on optimizing the workflow for managing multiple packages and dependencies, allowing developers to share code across projects, while Webpack is primarily used to bundle and optimize assets for web applications. 3. Configuration: Lerna uses a configuration file named lerna.json to define workspace configuration and manage package versioning, while Webpack uses a configuration file named webpack.config.js to define asset entry points, loaders, and output settings. 4. Features: Lerna provides features such as managing package dependencies, versioning, publishing, and running commands across multiple packages, while Webpack provides features such as code splitting, hot module replacement, and asset optimization. 5. Integration: Lerna works well with other tools in the JavaScript ecosystem such as npm and yarn, while Webpack can be integrated with other build tools and task runners like Gulp or Grunt. 6. Output: Lerna does not bundle or transform code but instead manages packages and their dependencies, while Webpack bundles and transforms code, optimizing it for deployment.

In Summary, Lerna is focused on managing multiple packages and their dependencies in a mono-repository, while Webpack is primarily used for bundling and optimizing assets for web applications.

Decisions about Lerna and Webpack
Aleksandr Filatov
Contract Software Engineer - Microsoft · | 4 upvotes · 293K views
Why migrated?

I could define the next points why we have to migrate:

  • Decrease build time of our application. (It was the main cause).
  • Also jspm install takes much more time than npm install.
  • Many config files for SystemJS and JSPM. For Webpack you can use just one main config file, and you can use some separate config files for specific builds using inheritance and merge them.
See more

We mostly use rollup to publish package onto NPM. For most all other use cases, we use the Meteor build tool (probably 99% of the time) for publishing packages. If you're using Node on FHIR you probably won't need to know rollup, unless you are somehow working on helping us publish front end user interface components using FHIR. That being said, we have been migrating away from Atmosphere package manager towards NPM. As we continue to migrate away, we may publish other NPM packages using rollup.

See more
Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of Lerna
Pros of Webpack
    Be the first to leave a pro
    • 309
      Most powerful bundler
    • 182
      Built-in dev server with livereload
    • 142
      Can handle all types of assets
    • 87
      Easy configuration
    • 22
      Laravel-mix
    • 4
      Overengineered, Underdeveloped
    • 2
      Makes it easy to bundle static assets
    • 2
      Webpack-Encore
    • 1
      Redundant
    • 1
      Better support in Browser Dev-Tools

    Sign up to add or upvote prosMake informed product decisions

    Cons of Lerna
    Cons of Webpack
      Be the first to leave a con
      • 15
        Hard to configure
      • 5
        No clear direction
      • 2
        Spaghetti-Code out of the box
      • 2
        SystemJS integration is quite lackluster
      • 2
        Loader architecture is quite a mess (unreliable/buggy)
      • 2
        Fire and Forget mentality of Core-Developers

      Sign up to add or upvote consMake informed product decisions

      What is Lerna?

      It is a popular and widely used package written in JavaScript. It optimizes the workflow around managing multi-package repositories with git and npm.

      What is Webpack?

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

      Need advice about which tool to choose?Ask the StackShare community!

      What companies use Lerna?
      What companies use Webpack?
      Manage your open source components, licenses, and vulnerabilities
      Learn More

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with Lerna?
      What tools integrate with Webpack?

      Sign up to get full access to all the tool integrationsMake informed product decisions

      What are some alternatives to Lerna and Webpack?
      Yarn
      Yarn caches every package it downloads so it never needs to again. It also parallelizes operations to maximize resource utilization so install times are faster than ever.
      Apache Maven
      Maven allows a project to build using its project object model (POM) and a set of plugins that are shared by all projects using Maven, providing a uniform build system. Once you familiarize yourself with how one Maven project builds you automatically know how all Maven projects build saving you immense amounts of time when trying to navigate many projects.
      Bit
      It is open source tool that helps you easily publish and manage reusable components. It help teams scale shared components to hundreds and even thousands of components, while eliminating the overhead around this process.
      Builder
      It is the first and only visual headless CMS with full drag and drop editing. It supports many frameworks like Angular, Vue, React, Preact etc. Convert Figma designs into clean code using Visual Copilot, leveraging AI into your workflow.
      Bazel
      Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google's software, and thus it has been designed to handle build problems present in Google's development environment.
      See all alternatives