Packer聽vs聽Webpack

Get Advice Icon

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

Packer
Packer

338
205
+ 1
40
Webpack
Webpack

11.2K
7.4K
+ 1
740
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.

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.
Get Advice Icon

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

Why do developers choose Packer?
Why do developers choose Webpack?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
    What companies use Packer?
    What companies use Webpack?

    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?
    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.
    AWS CloudFormation
    You can use AWS CloudFormation鈥檚 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鈥檛 need to figure out the order in which AWS services need to be provisioned or the subtleties of how to make those dependencies work.
    GeoEngineer
    GeoEngineer uses Terraform to plan and execute changes, so the DSL to describe resources is similar to Terraform's. GeoEngineer's DSL also provides programming and object oriented features like inheritance, abstraction, branching and looping.
    Pulumi
    Pulumi is a cloud development platform that makes creating cloud programs easy and productive. Skip the YAML and just write code. Pulumi is multi-language, multi-cloud and fully extensible in both its engine and ecosystem of packages.
    Habitat
    Habitat is a new approach to automation that focuses on the application instead of the infrastructure it runs on. With Habitat, the apps you build, deploy, and manage behave consistently in any runtime鈥夆斺塵etal, VMs, containers, and PaaS. You'll spend less time on the environment and more time building features.
    See all alternatives
    Decisions about Packer and Webpack
    John Kodumal
    John Kodumal
    CTO at LaunchDarkly | 3 upvotes 37.1K views
    atLaunchDarklyLaunchDarkly
    Armory
    Armory
    Packer
    Packer
    Terraform
    Terraform
    Spinnaker
    Spinnaker
    Ansible
    Ansible

    LaunchDarkly is almost a five year old company, and our methodology for deploying was state of the art... for 2014. We recently undertook a project to modernize the way we #deploy our software, moving from Ansible-based deploy scripts that executed on our local machines, to using Spinnaker (along with Terraform and Packer) as the basis of our deployment system. We've been using Armory's enterprise Spinnaker offering to make this project a reality.

    See more
    Tom谩拧 Pusteln铆k
    Tom谩拧 Pusteln铆k
    Webpack
    Webpack
    gulp
    gulp
    jQuery
    jQuery
    JavaScript
    JavaScript

    I use JavaScript these days and for few years I didn't have to use jQuery at all. I used to use it back in the days when IE8 and similar was a thing. But due to better browser support of native functions for DOM manipulation I could move to vanilla JavaScript. Most of the time, that's all I need to work with modals/accordions and similar. But I'm not saying that jQuery is bad. It was, and still is a great tool. Some of it's features are available in all browsers nowadays so it is not so important as it used to be. But jQuery has still advantage for example in it's selector engine, some DOM selections which are easy in jQuery are a bit more difficult in vanilla JS (you have to create some helper functions or use some 3rd party library to help you with that), but to be honest I needed this on very few occasions. So it really depends on your project (supported browses, plain JS or some bundling - gulp, Webpack, whether you plan to use modules etc.). Hope this helps.

    See more
    Gustavo Mu帽oz
    Gustavo Mu帽oz
    Web UI Developer at Globant | 4 upvotes 16.7K views
    Parcel
    Parcel
    gulp
    gulp
    Grunt
    Grunt
    Webpack
    Webpack
    #WebPackDevServer
    #Merge

    Using Webpack is one of the best decision ever. I have used to Grunt and gulp previously, but the experience is not the same, and despite I know there are other bundlers like Parcel, Webpack gives me the perfect balance between automatization and configuration. The ecosystem of tools and loaders is amazing, and with WebPack #merge, you can modularize your build and define standard pieces to assemble different build configurations. I don't like processes where you cannot see their guts, and you have to trust in magic a little bit too much for my taste. But also I don't want to reinvent the wheel and lose too much time configuring my build processes. And of course, I love #WebPackDevServer and hot reloading.

    See more
    Pedro Arnal Puente
    Pedro Arnal Puente
    CTO at La Cupula Music SL | 7 upvotes 51.3K views
    atLa Cupula Music SLLa Cupula Music SL
    Ansible
    Ansible
    Packer
    Packer
    Terraform
    Terraform
    Amazon ElastiCache
    Amazon ElastiCache
    Redis
    Redis
    Amazon RDS for Aurora
    Amazon RDS for Aurora
    Amazon S3
    Amazon S3
    Amazon EC2
    Amazon EC2
    Debian
    Debian

    Our base infrastructure is composed of Debian based servers running in Amazon EC2 , asset storage with Amazon S3 , and Amazon RDS for Aurora and Redis under Amazon ElastiCache for data storage.

    We are starting to work in automated provisioning and management with Terraform , Packer , and Ansible .

    See more
    Interest over time
    Reviews of Packer and Webpack
    No reviews found
    How developers use Packer and Webpack
    Avatar of Volkan 脰z莽elik
    Volkan 脰z莽elik uses WebpackWebpack

    Webpack is the best bundler. Period.

    Yes, it has a(n arguably) messy documentation, and a steep learning curve; but once you get the hang of it, there is nothing you cannot do with it.

    Use it and you don鈥檛 have to use any other bundler at all.

    It has a vivid ecosystem, and great plugin support.

    Avatar of Alec Cunningham
    Alec Cunningham uses WebpackWebpack

    My preferred build tool; allows me to bundle my JSX, JS, CSS files for easy access and I can pass the bundle through my node server for server side rendering.

    Avatar of Kent Steiner
    Kent Steiner uses WebpackWebpack

    Flexible building and compiling of source for browser consumption, mainly for JS, but experimenting a little with CSS (although I prefer StylusJS for CSS).

    Avatar of Andrew Gatenby
    Andrew Gatenby uses WebpackWebpack

    We use this to optimise the delivery of the client-side for our revised Admin System, so it's able to be delivered to browsers as efficiently as possible.

    Avatar of Cameron Drake
    Cameron Drake uses WebpackWebpack

    Webpack compiles files to bundles with source maps. Using Webpack you can use the latest features (ES6) and have it compiled to compliant js.

    Avatar of Bob P
    Bob P uses PackerPacker

    Packer makes it easy to setup custom images to import into vagrant.

    Avatar of Zinc
    Zinc uses PackerPacker

    We use Packer to build our Base AMIs.

    Avatar of Endource
    Endource uses PackerPacker

    Application deployment packages

    Avatar of Go Furuya
    Go Furuya uses PackerPacker

    To make the "Golden Image"

    Avatar of Scott Miller
    Scott Miller uses PackerPacker

    Used for packing AMIs

    How much does Packer cost?
    How much does Webpack cost?
    Pricing unavailable
    Pricing unavailable
    News about Packer
    More news