Parcel – A fast, zero configuration web application bundler

Came here to puff about &quot;yet another bundler&quot;.<p>Then read all of the docs in 15 minutes and realized that I might like this.<p>Then I used it and I know that I&#x27;ll keep using it, unless there are any showstoppers.<p>Great job, Devon!

Browserify, Webpack, Gulp, Grunt: everything nice and shiny, but the one JS lib that stands out for me is Rollup.js[1]<p>Why? Because Rollup.js makes it possible to structure code into modules in a way that is backwards compatible and future proof. Yeah it takes some getting used to and it is not yet as simple as it could be, because integrating libs which are not yet available in the module format, takes some manual configuration, but once you know how to use it you won&#x27;t want to got back.<p>I can highly recommend it, not because it is the hottest tool out there, but because I think it has a much higher long-term value than most JS libs.<p>Parcel seems to have a similar functionality but due to the wide range of other functions it comes with, I think there is a much higher chance that it will be rendered obsolete in the near future. Rollup.js on the other hand _focuses_ on the combination of modules to a single bundle which will continue to be required for the foreseeable future.<p>[1] <a href="https:&#x2F;&#x2F;rollupjs.org" rel="nofollow">https:&#x2F;&#x2F;rollupjs.org</a>

As a person who is not well-versed in front-end technology, it will be great if the author(s) could provide more comparison on the website against some other tools that serve the similar purpose in aspects other than performance. For instance the by comparing the scope the problem each solves, the ideology behind each project, or even a side by side configuration file.

The eternal cycle of developer tool bullshit:<p>1. &quot;Ugh, OldTool™ v3.0.0 is overcomplicated, bloated, slow and unnecessarily configurable!&quot;<p>2. &quot;Introducing SuperTool™ v1.0.0, which just does the stuff you really need. No bloated configuration. No huge ecosystem of extensions. Simple, straightforward and fast.&quot;<p>3. &quot;SuperTool™ v1.0.0 is great! But our setup really needs it to do something a bit different, so we&#x27;ve hacked in this extension.&quot;<p>...repeat for a while...<p>10. &quot;Introducing SuperTool™ v2.0.0, which now has a more flexible API and configuration , allowing many former hacks to be done in a straightforward way.&quot;<p>11. &quot;SuperTool™ v2.0.0 is great! But our setup really needs it to do something a bit different, so we&#x27;ve hacked in this extension.&quot;<p>...repeat for a while...<p>20. &quot;Introducing SuperTool™ v3.0.0, with a whole new, flexible, pipeline based API. Everything is a plugin! There&#x27;s even a plugin to send email!&quot;<p>21. &quot;Ugh, SuperTool™ v3.0.0 is overcomplicated, bloated, slow and unnecessarily configurable!&quot;<p>22. &quot;Introducing HyperTool™ v1.0.0, which just does the stuff you really need. No bloated configuration. No huge ecosystem of extensions. Simple, straightforward and fast.&quot;

I think it&#x27;s super cool.<p>I&#x27;ve been configuring Webpack projects for almost 2 years now and I&#x27;d rather use Parcel tbh. My only problem is the lack of plugins such as loading .vue files.

With transitive dependencies, the total install footprint for this is 689 packages weighing in at 77MB.<p>This isn&#x27;t reducing complexity, it&#x27;s just taking all the junk you&#x27;d normally have in your bloated boilerplate and putting it directly into the build tool. I&#x27;m not convinced that&#x27;s a good idea.

The two coolest things about Parcel for me, are 1) multi-core support, and 2) a simpler, ES6-esque API. Without these two distinct elements, I think Parcel is nothing more than a simple Webpack boilerplate which could easily been generated by yeoman.<p>I see its potential regarding Parcel’s competitiveness against Webpack, but it also has worsen the JavaScript fatigue, which is considered a nightmare for many newcomers webdevs because of huge fragmentation and thus bigotry in the industry.

Is my career as a Webpack whisperer at an end?<p><i>cries tears of joy</i><p>;-)

It would be nice if these bundlers could help publish npm packages that vend non-JS assets (html, stylesheets, fonts, images) in a way that&#x27;s easily consumed by other packages.<p>For example, if one of the JS modules in a library package says &quot;import classes from &#x27;.&#x2F;styles.scss&#x27;&quot; and an application package imports that JS module, the application should somehow end up with the CSS output from styles.scss without having to configure Sass itself, and without having to include the entire stylesheet from the library package.

I&#x27;ve been using <a href="http:&#x2F;&#x2F;brunch.io" rel="nofollow">http:&#x2F;&#x2F;brunch.io</a> and enjoying it. Far less configuration than Webpack.

I had my eye on <a href="http:&#x2F;&#x2F;fuse-box.org&#x2F;" rel="nofollow">http:&#x2F;&#x2F;fuse-box.org&#x2F;</a> for a while, and tried a few sample projects with it. It has a lot of the same promises as Parcel appears to have. Multicore is exciting for me, which Fusebox doesn&#x27;t have. So... many... choices...

It would be great if the author taken any of the HNPWA project and replaced WebPack with Parcel so you can compare the setup and actual configuration needed. WebPack is currently a standard and the community is great so I&#x27;m not seeing this replacing it in any way.

I have no problem with ditching webpack for another tool if it&#x27;s faster and of similar or better quality. Is anyone using this in production and want to share their experiences?

Should main.css be included in the index.html example?<p>This just confused me for some reason but it&#x27;s more me focusing on the wrong thing, haha

From the webpack team to Devon:<p>Thank you so much for this work! Not only are we happy to see a real contender in the bundling space, but also look forward to not only work together, but also learn from parcel in ways we can help make webpack more flexible and easy to use for those who want &quot;zero configuration&quot;.<p>Welcome to the bundler family!<p>Sean webpack team

Really happy that besides being fast they made a priority to keep the configuration simple.<p>I love webpack to death but there are just so many parts that I keep getting confused, esp with things like &quot;!&quot; in in require, always copy-pasting the same boilerplate code over and over to for sass, es6, etc. I know it may be more flexible but sometimes you just want things to work and can&#x27;t be bothered with too many details. Laravel did this with elixir where it wrote a wrapper just to do it (which lets you just get on with your work without having to learn another tool). This too seems to be focused on that. Great job!

Didn&#x27;t see any info that would give me an impression of the possibility if this getting any traction which I think would be even more important than any specific benefits.

This looks awesome!<p>After reading the docs though I couldn&#x27;t find any mention of tree-shaking or other things that would shrink the final bundle size. Any word on that front?

Looks like a well-thought-out approach to a clientside JS bundler.<p>Is this officially backed by one of the author&#x27;s employers or any other organization? I&#x27;ve seen too many projects (including major parts of bundlers browserify, gulp) die early when a sole author is forced to move on. Beyond the technical advantages, if I knew a company had already invested resources it would give me a solid business reason to switch.

I am not the target audience for this.<p>However, my first reaction was &quot;yet another build tool, huh?&quot;<p>My next thought was &quot;...I must be getting old.&quot;

Is anybody running a project with webpack that has a 20s rebuild time?<p>Or if somebody has switched from webpack to parcel, can they give an idea of the performance improvement?<p>We&#x27;ve got a moderate sized app, and webpack rebuild (typescript, server-side react, client side js bundle, css export) is less than 3 seconds.

&gt; Bundle all your assets<p>Can someone ELI5 what is bundling and what problem does it solve?

When one deploys something like this in production, how do you interact with an internal API? Surrendering control of my url routing always causes problems for me.

how does this handle existing 3rd party jquery plugins? The single biggest problem and configuration nightmare I always face is bundling something like CKeditor.

So far from comments I have collected following bundling tools:<p>- Webpack<p>- Rollup<p>- Fuse-Box<p>- Brunch<p>- Browserify

React and node bundling and compilation ?

Which bundler does this use?

Explain to me why do we web app need bundlers?

why are we not just using bash scripts ???<p>-you can log output -perfectly capable of handling your unique build style -no setup (pretty much) -just call the command lines of other tools like (less.c, yui-compressor.jar ... etc) for compliation tasks<p>talk about over engineering. The thing is that the reason we dont have 1 to rule them all now is because no one has ever objectively argued why one is better than the other.<p>If we could just get command line equilvalents for things like ember-cli that didnt require npm then we would be good. Npm is the thing holing us back , we dont need it to do command line processing. Its a bloated middle man. Please command line tool gods , offer your tool outside of the javascript eco system. Build it in java and export to jar or c and allow us to worry about the stitching<p>Question , what is the thing npm&#x2F;grunt&#x2F;gulp gives us that cannot be done with bash, if all the tools we used were command line executables?