BrowserStack vs Webpack

Overview

BrowserStack

Stacks2.7K

Followers2.0K

Votes533

Webpack

Stacks45.0K

Followers28.1K

Votes752

GitHub Stars65.7K

Forks9.2K

BrowserStack vs Webpack: What are the differences?

BrowserStack: Instant access to a lab of 1000+ real mobile and desktop browsers for testing. Live, Web-Based Browser Testing Instant access to all real mobile and desktop browsers. Say goodbye to your lab of devices and virtual machines; 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.

BrowserStack and Webpack are primarily classified as "Browser Testing" and "JS Build Tools / JS Task Runners" tools respectively.

"Multiple browsers", "Ease of use" and "Real browsers" are the key factors why developers consider BrowserStack; whereas "Most powerful bundler", "Built-in dev server with livereload" and "Can handle all types of assets" are the primary reasons why Webpack is favored.

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.

Airbnb, Instagram, and Pinterest are some of the popular companies that use Webpack, whereas BrowserStack is used by ebay, Typeform, and Wikipedia. Webpack has a broader approval, being mentioned in 2209 company stacks & 1344 developers stacks; compared to BrowserStack, which is listed in 579 company stacks and 239 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 BrowserStack, Webpack

Rinchin

Jul 20, 2020

Needs adviceon

Selenium

Sauce Labs

I am looking to purchase one of these tools for Mobile testing for my team. It should support Native, hybrid, and responsive app testing. It should also feature debugging, parallel execution, automation testing/easy integration with automation testing tools like Selenium, and the capability to provide availability of devices specifically for us to use at any time with good speed of performing all these activities.

I have already used Perfecto mobile, and Sauce Labs in my other projects before. I want to know how different or better is AWS Device farm in usage and how advantageous it would be for us to use it over other mentioned tools

217k views217k

Comments

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

BrowserStack	Webpack
BrowserStack is the leading test platform built for developers & QAs to expand test coverage, scale & optimize testing with cross-browser, real device cloud, accessibility, visual testing, test management, and test observability.	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 instant access to 20,000+ real mobile devices and browsers, which include real iOS and Android devices, Chrome, IE, Firefox, Safari; Test websites hosted on internal dev and staging environments with zero setup or configuration; Run hundreds of tests concurrently to speed up the execution time of your test suite by more than 10x	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
Statistics
GitHub Stars -	GitHub Stars 65.7K
GitHub Forks -	GitHub Forks 9.2K
Stacks 2.7K	Stacks 45.0K
Followers 2.0K	Followers 28.1K
Votes 533	Votes 752
Pros & Cons
Pros 135 Multiple browsers 76 Ease of use 65 Real browsers 44 Ability to use it locally 27 Good price Cons 2 Very limited choice of minor versions	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 Fire and Forget mentality of Core-Developers 2 Loader architecture is quite a mess (unreliable/buggy) 2 SystemJS integration is quite lackluster
Integrations
Cypress QMetry Jira WordPress Shopify Zapier Drone.io Jenkins Slack GitLab	JavaScript

What are some alternatives to BrowserStack, Webpack?

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.

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.

Selenium

Selenium automates browsers. That's it! What you do with that power is entirely up to you. Primarily, it is for automating web applications for testing purposes, but is certainly not limited to just that. Boring web-based administration tasks can (and should!) also be automated as well.

Sauce Labs

Cloud-based automated testing platform enables developers and QEs to perform functional, JavaScript unit, and manual tests with Selenium or Appium on web and mobile apps. Videos and screenshots for easy debugging. Secure and CI-ready.

LambdaTest

LambdaTest platform provides secure, scalable and insightful test orchestration for website, and mobile app testing. Customers at different points in their DevOps lifecycle can leverage Automation and/or Manual testing on LambdaTest.

Karma

Karma is not a testing framework, nor an assertion library. Karma just launches a HTTP server, and generates the test runner HTML file you probably already know from your favourite testing framework. So for testing purposes you can use pretty much anything you like.

Playwright

It is a Node library to automate the Chromium, WebKit and Firefox browsers with a single API. It enables cross-browser web automation that is ever-green, capable, reliable and fast.

Rainforest QA

Rainforest gives you the reliability of a QA team and the speed of automation, without the hassle of managing a team or the pain of writing automated tests.

WebdriverIO

WebdriverIO lets you control a browser or a mobile application with just a few lines of code. Your test code will look simple, concise and easy to read.

Brunch

Brunch is an assembler for HTML5 applications. It's agnostic to frameworks, libraries, programming, stylesheet & templating languages and backend technology.

Related Comparisons

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.

BrowserStack vs Webpack