Recently I was publishing a library to npm and I thought of experimenting with the bundler I was going to package my code in. i see zero reasons not to work with it in small nor big projects. Moreover, fetching a minified file weighing a few KBs is faster than the actual file, which might run into MBs, resulting in improved load time of the app.Sure you can, but when working with huge codebases, minifying the app manually isn’t a scalable solution. Parcel, on the other hand doesn’t require any config file to be specified. For example linking to a typescript file instead of a js file. ), but there are some few more steps and will get started with them.After installing Webpack, you need to create a file called A very basic Webpack configuration looks like this (from the official website):Then you can start Webpack to watch over your files.But what happens in Parcel is crazy, you only need to create an I mark Parcel 10, but Webpack has to stick with 8 here.We'll the next major thing about using a bundler is the help you need with your preprocessors like Sass or Less.Well, this is how you should configure Webpack to recognize your preprocessors:Although this might look scary, it isn't that hard, to be honest.What about Parcel? One might argue that Parcel in many cases offers built-in configurations that might provide ease of development, but it’s difficult to overlook the extensive support and customisability that webpack provides.At the end of the day, it’s a personal call that every developer needs to make based on their requirements. Use it if you want with a link to this page in case that doesn't cause you any problem.I'm Adnan Babakan and I'm from Iran. The “configuration” of parcel really comes from the fact you directly include the files you need within the entry point as if they worked native. But there are issues associated with it when using HTTP logging, Hooks, and middleware.When using Rollup, we need to install and configureWith webpack, you just need to add one plugin, called Hot module replacement (HMR) improves the development experience by automatically updating modules in the browser at run time without needing a whole page refresh. What if I want to customize something? If you have used webpack 3 before, you know of webpack.config. So you don't have to do anything. The efficiency of this transmission is directly proportional to the number and size of the files being requested. We're a place where coders share, stay up-to-date and grow their careers. I know it can be scary at the beginning (even though after introducing version 2 it's really simple), so a lot of folks will be looking for alternatives. To create even a minimal project, you need a webpack.config file. If you want the control, that is fine. But for production usage, I think Webpack is a standard for a reason.I want to try parcel, but webpack is too easy since it lives in nearly every JavaScript framework's project template without needing to configure it yourself.A constructive and inclusive social network. It’s not a winner take all situation. So this is only a personal point of view. Where as webpack has a much larger surface area. Parcel is a web application bundler, differentiated by its developer experience. A bundler with live reload capability does that refreshing for you.Bundlers provide you with a run-time environment in addition to other utilities essential for debugging and development, in the form of a development server.Parcel has been very thoughtful by having a development server built in, which will automatically rebuild your app as you change files. Use Parcel.Building a library with minimal third-party imports? Here code splitting is controlled by use of the dynamic It was tempting to favour Rollup and Parcel over webpack for code splitting, but both of them have only recently introduced this feature and some issues have also been reported. I would recommend using Parcel for small to medium scaled projects, and Webpack beyond that. I've tried Parcel some time ago and it was cool, but the fact it lacks configuration is a flaw in my opinion. For example, if you were five levels deep into your app navigation and saved a change, live reloading would restart the app altogether and load it back to the landing/initial route.Hot reloading, on the other hand, only refreshes the files that were changed while still maintaining the state of the app. ), but there are some few more steps and will get started with them. You would not bundle sever files with parcel for example. Huge and heavy files cannot be loaded fast, and a website being slow won't be something that your client or visitor would want to have.As the previous sections, Parcel claims to support code splitting with zero configuration, and that's true.Both of them support dynamic imports, and that's good.BUT HERE IS THE PROBLEM THAT IS LITERALLY ANNOYING.This is very neat and clean, it needs some configuration though to split your dynamic components, but it isn't that hard.Everything is in its appropriate folder, images, CSS, JavaScript, and even fonts.To be fair because of the no configuration feature, Parcel has I give it a 2, and Webpack gets a 9 in this section.Webpack is famous, and lots of frameworks use Webpack as their bundler such as my beloved Nuxt.js.