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

Packer

540
501
+ 1
42
Webpack

32.8K
22.2K
+ 1
750
Add tool

Packer vs Webpack: What are the differences?

Developers describe Packer as "Create identical machine images for multiple platforms from a single source configuration". Packer automates the creation of any type of machine image. It embraces modern configuration management by encouraging you to use automated scripts to install and configure the software within your Packer-made images. On the other hand, Webpack is detailed as "A bundler for javascript and friends". 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.

Packer and Webpack are primarily classified as "Infrastructure Build" and "JS Build Tools / JS Task Runners" tools respectively.

"Cross platform builds" is the primary reason why developers consider Packer over the competitors, whereas "Most powerful bundler" was stated as the key factor in picking Webpack.

Packer and Webpack are both open source tools. It seems that Webpack with 49.8K GitHub stars and 6.27K forks on GitHub has more adoption than Packer with 9.1K GitHub stars and 2.47K GitHub forks.

Airbnb, Instagram, and Pinterest are some of the popular companies that use Webpack, whereas Packer is used by Instacart, Oscar Health, and Razorpay. Webpack has a broader approval, being mentioned in 2209 company stacks & 1342 developers stacks; compared to Packer, which is listed in 115 company stacks and 21 developer stacks.

Decisions about Packer and Webpack
Aleksandr Filatov
Contract Software Engineer - Microsoft · | 4 upvotes · 130.7K 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
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Packer
Pros of Webpack
  • 27
    Cross platform builds
  • 9
    Vm creation automation
  • 4
    Bake in security
  • 1
    Good documentation
  • 1
    Easy to use
  • 308
    Most powerful bundler
  • 182
    Built-in dev server with livereload
  • 142
    Can handle all types of assets
  • 87
    Easy configuration
  • 21
    Laravel-mix
  • 4
    Overengineered, Underdeveloped
  • 2
    Webpack-Encore
  • 2
    Makes it easy to bundle static assets
  • 1
    Redundant
  • 1
    Better support in Browser Dev-Tools

Sign up to add or upvote prosMake informed product decisions

Cons of Packer
Cons of Webpack
    Be the first to leave a con
    • 12
      Hard to configure
    • 3
      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

    - No public GitHub repository available -

    What is Packer?

    Packer automates the creation of any type of machine image. It embraces modern configuration management by encouraging you to use automated scripts to install and configure the software within your Packer-made images.

    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 Packer?
    What companies use Webpack?
    See which teams inside your own company are using Packer or Webpack.
    Sign up for Private StackShareLearn More

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

    What tools integrate with Packer?
    What tools integrate with Webpack?

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

    What are some alternatives to Packer and Webpack?
    Docker
    The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere
    Terraform
    With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.
    Vagrant
    Vagrant provides the framework and configuration format to create and manage complete portable development environments. These development environments can live on your computer or in the cloud, and are portable between Windows, Mac OS X, and Linux.
    Ansible
    Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use.
    AWS CloudFormation
    You can use AWS CloudFormation’s sample templates or create your own templates to describe the AWS resources, and any associated dependencies or runtime parameters, required to run your application. You don’t need to figure out the order in which AWS services need to be provisioned or the subtleties of how to make those dependencies work.
    See all alternatives