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

AWS CodeCommit

327
820
+ 1
193
Webpack

39.9K
27K
+ 1
752
Add tool

AWS CodeCommit vs Webpack: What are the differences?

AWS CodeCommit: Fully-managed source control service that makes it easy for companies to host secure and highly scalable private Git repositories. CodeCommit eliminates the need to operate your own source control system or worry about scaling its infrastructure. You can use CodeCommit to securely store anything from source code to binaries, and it works seamlessly with your existing Git tools; 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 CodeCommit and Webpack are primarily classified as "Code Collaboration & Version Control" and "JS Build Tools / JS Task Runners" tools respectively.

"Free private repos" is the top reason why over 39 developers like AWS CodeCommit, while over 307 developers mention "Most powerful bundler" as the leading cause for choosing 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 2208 company stacks & 1340 developers stacks; compared to AWS CodeCommit, which is listed in 25 company stacks and 17 developer stacks.

Decisions about AWS CodeCommit and Webpack
Aleksandr Filatov
Contract Software Engineer - Microsoft · | 4 upvotes · 280.9K 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 StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of AWS CodeCommit
Pros of Webpack
  • 44
    Free private repos
  • 26
    IAM integration
  • 24
    Pay-As-You-Go Pricing
  • 20
    Amazon feels the most Secure
  • 19
    Repo data encrypted at rest
  • 11
    Faster deployments when using other AWS services
  • 11
    I can make repository by myself if I have AWS account
  • 8
    AWS CodePipeline integration
  • 6
    Codebuild integration
  • 6
    Does not support web hooks yet! :(
  • 4
    Cost Effective
  • 2
    No Git LFS! Dealbreaker for me
  • 2
    Integrated with AWS Ecosystem
  • 2
    Elastic Beanstalk Integration
  • 1
    Integration via SQS/SNS for events (replaces webhooks)
  • 1
    IAM
  • 1
    Open source friendly
  • 1
    Only US Region
  • 1
    Available in Ireland (Dublin) region
  • 1
    CodeDeploy Integration
  • 1
    Issue tracker
  • 1
    CodeCommit Trigger for an AWS Lambda Function
  • 0
    Ui
  • 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 AWS CodeCommit
Cons of Webpack
  • 12
    UI sucks
  • 4
    SLOW
  • 3
    No Issue Tracker
  • 2
    Bad diffing/no blame
  • 2
    NO LFS support
  • 2
    No fork
  • 2
    No webhooks
  • 1
    Can't download file from UI
  • 1
    Only time based triggers
  • 0
    Accident-prone UI
  • 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

- No public GitHub repository available -

What is AWS CodeCommit?

CodeCommit eliminates the need to operate your own source control system or worry about scaling its infrastructure. You can use CodeCommit to securely store anything from source code to binaries, and it works seamlessly with your existing Git tools.

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!

Jobs that mention AWS CodeCommit and Webpack as a desired skillset
What companies use AWS CodeCommit?
What companies use Webpack?
See which teams inside your own company are using AWS CodeCommit or Webpack.
Sign up for StackShare EnterpriseLearn More

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

What tools integrate with AWS CodeCommit?
What tools integrate with Webpack?

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

What are some alternatives to AWS CodeCommit and Webpack?
GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.
GitLab
GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.
Bitbucket
Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users.
GitHub Enterprise
GitHub Enterprise lets developers use the tools they love across the development process with support for popular IDEs, continuous integration tools, and hundreds of third party apps and services.
SVN (Subversion)
Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations.
See all alternatives