81–90 of 103 posts
Very unclear what it does, until I tried to copy/paste the title. That changing word should just be a list.
Earlier quoted context omitted.
Note that Devon Govett, who you replied to, is the main driving force behind Parcel.
And? I just looked up my old package.json and see the NPM script use `parcel build --no-autoinstall ...` and a pinned version `2.0.0-beta.3.1` which to me says there some genuine autoinstall going on, which is what I meant by "implicit plugin loading", loading/installing some plugins from the ether. Perhaps my wording wasn't clear, but it still was an issue for me. Parcel in my experience still came with less issues…
Earlier quoted context omitted.
A free open source tool exists for you to use if it suits your needs. What exactly is the "real problem" here?
>A free open source tool exists for you to use if it suits your needs. I do not believe that webpack suits my needs, it is in my opinion incredibly inferior to Gulp. So Gulp suits my needs. Nonetheless I have had to basically use nothing but webpack for the last 5-6 years unless I do something for myself! Why is that? Well it turns out that when I go to work at some place they have set up everything with webpack, why…
Earlier quoted context omitted.
>A free open source tool exists for you to use if it suits your needs. I do not believe that webpack suits my needs, it is in my opinion incredibly inferior to Gulp. So Gulp suits my needs. Nonetheless I have had to basically use nothing but webpack for the last 5-6 years unless I do something for myself! Why is that? Well it turns out that when I go to work at some place they have set up everything with webpack, why…
I'm still not understanding the problem. If webpack doesn't suit your needs then don't use it. If your employer's technical leadership picks technologies based on fashion rather than suitability for the problem that's not a failure of the technology, that same problem surrounds literally every popular technology irrespective of its technical properties.
My poop is on the street. If you like it, you can use it. If you don't like, don't use it. What's your problem? If someone shoves my poop down your throat and you don't like it, that's not a failure of my poop. That's a failure of human relationships.
Previous thread: Parcel 2 Beta 3 – improved build performance - https://news.ycombinator.com/item?id=27222460 - May 2021 (69 comments) Also related: Parcel – Fast, zero-configuration web application bundler - https://news.ycombinator.com/item?id=21961963 - Jan 2020 (201 comments) Parcel: Fast, zero configuration web application bundler - https://news.ycombinator.com/item?id=17547433 - July 2018 (91 comments) Parcel –…
Esbuild – An extremely fast JavaScript bundler
Earlier quoted context omitted.
What do you mean by "dev/validation iteration"?
Say you're developing a big form with lots of different inputs. When you're iterating on the form you don't want to lose all your form state because you edited some code. When you make the change you want to see what that change does to your form in its current state.
That's why things like mock-service-worker or having prefilled Redux stores (or whatever state management you use that allows something similar) are a real time saver.
Of course fixing the bug based on test is always better, but often you have to fix something visual which is a little bit harder to do with tests.
> The zero configuration build tool for the web.JavaScript.CSS.HTML.TypeScript.React.images.SASS.SVG.Vue.libraries.Less.CoffeeScript.Node.Stylus.Pug.Electron.Elm.WebGL.extensions.GraphQL.MDX.XML. Parcel combines a great out-of-the-box development experience with a scalable architecture that can take your project from just getting started to massive production application. Very unclear what it does, until I tried to c…
The selling point for parcel is that it does the above with zero configuration (you point it at your input directory and it automatically figures out which compilers / optimisers to use -- other builders typically require hours of googling for / installing / configuring / debugging plugins)
Earlier quoted context omitted.
I'm still not understanding the problem. If webpack doesn't suit your needs then don't use it. If your employer's technical leadership picks technologies based on fashion rather than suitability for the problem that's not a failure of the technology, that same problem surrounds literally every popular technology irrespective of its technical properties.
Are you serious? Here's how you sound to me: My poop is on the street. If you like it, you can use it. If you don't like, don't use it. What's your problem? If someone shoves my poop down your throat and you don't like it, that's not a failure of my poop. That's a failure of human relationships.
Earlier quoted context omitted.
What do you mean by "dev/validation iteration"?
Say you're developing a big form with lots of different inputs. When you're iterating on the form you don't want to lose all your form state because you edited some code. When you make the change you want to see what that change does to your form in its current state.
> An all new plugin system, which makes Parcel fully extensible. This allows Parcel to scale from small side projects to massive production applications with complex build requirements. Everything old is new again! Parcel embarks on the path that Webpack did, and it's only a matter of time before the plugins are doing more and more core work, and Parcel's successor will again rewrite them and bring those in to the co…
And Webpack embarked on the path that it’s forefathers did.. gulp, babel, browserify, grunt, and others. But that didn’t stop Webpack from improving on what was there.
The core thing Parcel does (or at least did when Parcel was started) that is/was a fundamental improvement over Webpack is parse your index.html (or whatever you name it, of course) to figure out what to do. I always thought Webpack was silly for asking a human to re-describe it’s html dependencies. I haven’t used Webpack in the last year, so I’m unaware if Webpack has fixed this shortcoming.