AWS CodeBuild vs Webpack

Overview

Webpack

Stacks45.0K

Followers28.1K

Votes752

GitHub Stars65.7K

Forks9.2K

AWS CodeBuild

Stacks443

Followers485

Votes43

AWS CodeBuild vs Webpack: What are the differences?

AWS CodeBuild: Build and test code with continuous scaling. AWS CodeBuild is a fully managed build service that compiles source code, runs tests, and produces software packages that are ready to deploy. With CodeBuild, you don’t need to provision, manage, and scale your own build servers; Webpack: 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.

AWS CodeBuild and Webpack are primarily classified as "Continuous Integration" and "JS Build Tools / JS Task Runners" tools respectively.

"Pay per minute" is the primary reason why developers consider AWS CodeBuild over the competitors, whereas "Most powerful bundler" was stated as the key factor in picking Webpack.

Webpack is an open source tool with 49.8K GitHub stars and 6.27K GitHub forks. Here's a link to Webpack's open source repository on GitHub.

According to the StackShare community, Webpack has a broader approval, being mentioned in 2206 company stacks & 1338 developers stacks; compared to AWS CodeBuild, which is listed in 21 company stacks and 14 developer stacks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Webpack, AWS CodeBuild

Aleksandr

Contract Software Engineer - Microsoft at Microsoft-365

Dec 23, 2019

Decided

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.

301k views301k

Comments

Abigail

Dec 10, 2019

Decided

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.

224k views224k

Comments

Detailed Comparison

Webpack	AWS CodeBuild
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.	AWS CodeBuild is a fully managed build service that compiles source code, runs tests, and produces software packages that are ready to deploy. With CodeBuild, you don’t need to provision, manage, and scale your own build servers.
Bundles ES Modules, CommonJS, and AMD modules (even combined); Can create a single bundle or multiple chunks that are asynchronously loaded at runtime (to reduce initial loading time); Dependencies are resolved during compilation, reducing the runtime size; Loaders can preprocess files while compiling, e.g. TypeScript to JavaScript, Handlebars strings to compiled functions, images to Base64, etc; Highly modular plugin system to do whatever else your application requires	Fully Managed Build Service;Continuous Scaling;Enables Continuous Integration;Integrates seamlessly with AWS services;FAQs: https://aws.amazon.com/codebuild/faqs/
Statistics
GitHub Stars 65.7K	GitHub Stars -
GitHub Forks 9.2K	GitHub Forks -
Stacks 45.0K	Stacks 443
Followers 28.1K	Followers 485
Votes 752	Votes 43
Pros & Cons
Pros 309 Most powerful bundler 182 Built-in dev server with livereload 142 Can handle all types of assets 87 Easy configuration 22 Laravel-mix Cons 15 Hard to configure 5 No clear direction 2 SystemJS integration is quite lackluster 2 Fire and Forget mentality of Core-Developers 2 Loader architecture is quite a mess (unreliable/buggy)	Pros 7 Pay per minute 5 Parameter Store integration for passing secrets 4 Integrated with AWS 3 Streaming logs to Amazon CloudWatch 3 Bit bucket integration Cons 2 Poor branch support
Integrations
JavaScript	AWS Elastic Beanstalk AWS CodeCommit Amazon S3 GitHub Bitbucket AWS CloudFormation Jenkins GitHub Enterprise

What are some alternatives to Webpack, AWS CodeBuild?

Jenkins

In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

gulp

Build system automating tasks: minification and copying of all JavaScript files, static images. More capable of watching files to automatically rerun the task when a file changes.

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

CircleCI

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

Grunt

The less work you have to do when performing repetitive tasks like minification, compilation, unit testing, linting, etc, the easier your job becomes. After you've configured it, a task runner can do most of that mundane work for you—and your team—with basically zero effort.

TeamCity

TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Related Comparisons

Bitbucket vs GitHub vs GitLab

AWS CodeCommit vs Bitbucket vs GitHub

Docker Swarm vs Kubernetes vs Rancher

Grunt vs Webpack vs gulp

Grafana vs Graphite vs Kibana

AWS CodeBuild vs Webpack: What are the differences?

AWS CodeBuild and Webpack are primarily classified as "Continuous Integration" and "JS Build Tools / JS Task Runners" tools respectively.

"Pay per minute" is the primary reason why developers consider AWS CodeBuild over the competitors, whereas "Most powerful bundler" was stated as the key factor in picking Webpack.

Webpack is an open source tool with 49.8K GitHub stars and 6.27K GitHub forks. Here's a link to Webpack's open source repository on GitHub.