Need advice about which tool to choose?Ask the StackShare community!
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.
What is BrowserStack?
What is Webpack?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose BrowserStack?
Why do developers choose Webpack?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using BrowserStack?
What are the cons of using Webpack?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Webpack?
Sign up to get full access to all the tool integrationsMake informed product decisions
BrowserStackIt's incredible how much this service has increased my productivity when it comes to testing new features in multiple browsers. And not only multiple browsers, multiple operating systems as well! And really LOVE that you can run it locally.
BrowserStackWe only really need this for IE support
WebpackWebpack 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’t have to use any other bundler at all.
It has a vivid ecosystem, and great plugin support.
BrowserStackWe use BrowserStack to run end to end tests with Selenium on our dashboard. It runs automatically before every deployment and cancels it if anything is out of place.
WebpackMy 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.
WebpackFlexible building and compiling of source for browser consumption, mainly for JS, but experimenting a little with CSS (although I prefer StylusJS for CSS).
WebpackWe 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.
WebpackWebpack compiles files to bundles with source maps. Using Webpack you can use the latest features (ES6) and have it compiled to compliant js.
BrowserStackBrowserStack is used by our development and support teams during QA and to try and reproduce bugs.
BrowserStackManually and automatically test our web and mobile apps.
BrowserStackQA tool to access to all desktop and mobile browsers.
BrowserStackUsed for cross browser scripting especially IE9 :-(