Need advice about which tool to choose?Ask the StackShare community!
Decisions about gulp, Pika Pack, and Webpack
Aleksandr Filatov
Contract Software Engineer - Microsoft · | 4 upvotes · 279.8K 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 installtakes much more time thannpm 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.
Abigail Watson
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.
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn MorePros of gulp
Pros of Pika Pack
Pros of Webpack
Pros of gulp
- Build speed451
- Readable277
- Code-over-configuration244
- Open source210
- Node streams175
- Intuitive107
- Lots of plugins83
- Works great with browserify66
- Easy to Learn45
- Laravel-elixir17
- build workflow4
- Simple & flexible3
- Great community3
- Stylus intergration2
- Clean Code2
- jade intergration2
- Well documented0
Pros of Pika Pack
Be the first to leave a pro
Pros of Webpack
- Most powerful bundler309
- Built-in dev server with livereload182
- Can handle all types of assets142
- Easy configuration87
- Laravel-mix22
- Overengineered, Underdeveloped4
- Makes it easy to bundle static assets2
- Webpack-Encore2
- Redundant1
- Better support in Browser Dev-Tools1
Sign up to add or upvote prosMake informed product decisions
Cons of gulp
Cons of Pika Pack
Cons of Webpack
Cons of gulp
Be the first to leave a con
Cons of Pika Pack
Be the first to leave a con
Cons of Webpack
- Hard to configure15
- No clear direction5
- Spaghetti-Code out of the box2
- SystemJS integration is quite lackluster2
- Loader architecture is quite a mess (unreliable/buggy)2
- Fire and Forget mentality of Core-Developers2
Sign up to add or upvote consMake informed product decisions
- No public GitHub repository available -
What is 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.
What is Pika Pack?
@pika/pack connects pre-configured plugins to build and optimize your package for you. Plugins wrap already-popular tools like Babel and Rollup with options already optimized for npm. This lets @pika/pack build your package without much (if any) configuration required on your part.
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 gulp, Pika Pack, and Webpack as a desired skillset
What companies use gulp?
What companies use Pika Pack?
What companies use Webpack?
What companies use gulp?
What companies use Pika Pack?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with gulp?
What tools integrate with Pika Pack?
What tools integrate with Webpack?
What tools integrate with gulp?
What tools integrate with Pika Pack?
What tools integrate with Webpack?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+31 28
36770
+46 27
32611
+39 22
31500
+43 18
5235
+42 53
21847
+25 7
3155
+27 13
5600
+35 13
1734
What are some alternatives to gulp, Pika Pack, and Webpack?
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.
npm
npm is the command-line interface to the npm ecosystem. It is battle-tested, surprisingly flexible, and used by hundreds of thousands of JavaScript developers every day.
Yarn
Yarn caches every package it downloads so it never needs to again. It also parallelizes operations to maximize resource utilization so install times are faster than ever.
CodeKit
Process Less, Sass, Stylus, Jade, Haml, Slim, CoffeeScript, Javascript, and Compass files automatically each time you save. Easily set options for each language.
Parcel
Parcel is a web application bundler, differentiated by its developer experience. It offers blazing fast performance utilizing multicore processing, and requires zero configuration.