Show HN: Jetpack – Webpack made more convenient

Cool. I wouldn&#x27;t take the critics too harshly. As someone who has configured a lot of webpack configs across multiple version of webpack and various versions of the plugins necessary to enable these features, I know <i>exactly</i> what you had in mind when you put this together. This is a very saturated technology stack, so people can&#x27;t help but react to it as noise.<p>To the critics, in front-end land there are some programmers who believe that building an SPA is always a mistake. I am of the opinion that there are some types of applications that live in the browser that benefit from the UX enhancements that scripting can provide. We all know some examples.<p>Everyone knows that front-end land is a crazy wild-west with a lot of moving and a lot of breaking along with a lot of hype, trends, wheel-reinventing and cavalier attitudes towards security. The criticisms are mostly fair.<p>However, if you&#x27;re building an SPA, there is a combination of tools out there that can provide a very conceptually clean (from an architectural perspective), performant, reusable, and highly productive and fun development experience. Of course, this doesn&#x27;t mean these tools make building an SPA the appropriate engineering decision, they are just tools, only the requirements can dictate whether or not an SPA should be built.<p>This project attempts to preconfigure via webpack, what is IMO, the best selection of tools available for working on an SPA today. For me, these tools include:<p><pre><code> - react - react SSR - bundle code-splitting - es6 (or ts&#x2F;es6+flow) - es6 modules - hot code and css reloading - module aliasing - css modules - postcss - reusing business and validation logic modules on the front and back end </code></pre> All of these tools solve very specific (former) problems that one encounters while working on an SPA. Anyway, nice work!

Woof sometimes HN can be pretty unforgiving. Remember the human guys. Good job man. Keep it up. Thanks for contributing to open source.

Hey just fyi in case you don&#x27;t know, jetpack[1] is the name of a very well known wordpress plugin by Automatic. Might cause some confusion.<p>[1] <a href="https:&#x2F;&#x2F;wordpress.org&#x2F;plugins&#x2F;jetpack&#x2F;" rel="nofollow">https:&#x2F;&#x2F;wordpress.org&#x2F;plugins&#x2F;jetpack&#x2F;</a>

Haven&#x27;t looked deeper in it, but why does it happen all the time that people think they can fix complexity by adding another layer of complexity too it?

<i>Run anywhere without installing locally, just like nodemon.</i><p>I npm install everything locally, never globally, and use npm run script to easily execute (and chain) stuff.<p>Am I in the minority?

How does this fare against <i>parcel-bundler</i> (<a href="https:&#x2F;&#x2F;parceljs.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;parceljs.org&#x2F;</a>)? It does pretty much the same thing in a slightly different manner, and I&#x27;d like to know before I actually consider giving it a try.<p>Thanks!<p>[1]:

And then weirdly you have also <i>this</i> alternative to webpack from the Elm community:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;NoRedInk&#x2F;jetpack" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;NoRedInk&#x2F;jetpack</a><p>Also called Jetpack...

There are a lot of &quot;configuration-free&quot; Webpack solutions popping up. The one thing that they all have in common is optional configuration.

We already have parcel.js which does all of this really well.

What was the motivation for this given existence of CRA? What are the main differences?

Isn’t that the name of a Wordpress plugin?<p><a href="https:&#x2F;&#x2F;wordpress.org&#x2F;plugins&#x2F;jetpack&#x2F;" rel="nofollow">https:&#x2F;&#x2F;wordpress.org&#x2F;plugins&#x2F;jetpack&#x2F;</a>

Do you know what else works almost without configuration, it&#x27;s fast and produces small minifiable bundles? Browserify.