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

Prepros

24
39
+ 1
21
Webpack

39.9K
27K
+ 1
752
Add tool

Prepros vs Webpack: What are the differences?

Key Differences between Prepros and Webpack

  1. Build systems: Prepros is primarily a static site generator that focuses on preprocessing tasks such as compiling Sass, Less, Stylus, and CoffeeScript, optimizing images, and refreshing browsers automatically. On the other hand, Webpack is a module bundler that efficiently packages and manages JavaScript modules along with their dependencies, providing advanced capabilities like code splitting, lazy loading, and hot module replacement.

  2. Configuration: Prepros has a graphical user interface (GUI) that allows developers to configure project settings through a visual interface, making it easier to set up and manage projects without diving into complex configuration files. Webpack, on the other hand, requires developers to create a configuration file (typically named webpack.config.js) where they define various aspects of the build process, such as entry points, loaders, plugins, and output settings.

  3. Extensibility: Prepros offers a limited number of built-in features and does not provide an official plugin system, limiting the extensibility options for developers. Webpack, on the other hand, has a rich ecosystem of plugins and loaders that can be easily integrated into the build process, allowing developers to customize every aspect of the bundling and optimization process according to their specific needs.

  4. Code Splitting: Prepros does not offer built-in code splitting capabilities, which means that all the JavaScript and CSS files are typically bundled into a single file. In contrast, Webpack provides native support for code splitting, allowing developers to split their code into multiple smaller chunks that can be loaded on-demand, resulting in faster initial page loads and reduced bandwidth usage.

  5. Hot Module Replacement (HMR): Prepros does not support hot module replacement, which is a feature that allows developers to update modules in real time without refreshing the entire page during development. In Webpack, HMR is built-in and can be easily configured, improving the development workflow by enabling faster iteration and providing instant feedback on code changes.

  6. Community Support: Prepros has a smaller user community compared to Webpack, which means that finding help, documentation, and community-created plugins or loaders might be more challenging. Webpack, being widely adopted and actively developed by a large community, offers extensive documentation, tutorials, forums, and a wide range of third-party plugins and loaders, making it easier to find support and resources when facing issues or trying to implement advanced features.

In Summary, Prepros is a user-friendly tool primarily focused on preprocessing tasks, while Webpack is a powerful module bundler offering advanced features like code splitting, hot module replacement, and extensive customization options through its configuration file and plugin system. Webpack's larger community and ecosystem make it a popular choice for complex build processes and highly modular applications.

Decisions about Prepros and Webpack
Aleksandr Filatov
Contract Software Engineer - Microsoft · | 4 upvotes · 280.2K 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 Prepros
Pros of Webpack
  • 4
    Easy to use
  • 4
    Beautiful GUI
  • 4
    Easy to configure
  • 3
    FTP upload
  • 2
    Freemium
  • 2
    Live reload
  • 2
    Any editor OK
  • 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 Prepros
Cons of Webpack
    Be the first to leave a con
    • 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 Prepros?

    It is an interface tool which handles pre-processing, and other front-end tasks. Its greatest strength is the incredible ease with which it allows you to use pre-processors of various kinds, be they for CSS, HTML or JavaScript.

    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!

    What companies use Prepros?
    What companies use Webpack?
    See which teams inside your own company are using Prepros 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 Prepros?
    What tools integrate with Webpack?

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

    What are some alternatives to Prepros and Webpack?
    CodeKit
    Process Less, Sass, Stylus, Jade, Haml, Slim, CoffeeScript, Javascript, and Compass files automatically each time you save. Easily set options for each language.
    Compass
    The compass core framework is a design-agnostic framework that provides common code that would otherwise be duplicated across other frameworks and extensions.
    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.
    LiveReload
    LiveReload monitors changes in the file system. As soon as you save a file, it is preprocessed as needed, and the browser is refreshed.
    BrowserSync
    BrowserSync makes your tweaking and testing faster by synchronising file changes and interactions across multiple devices. It’s wicked-fast and totally free.
    See all alternatives