4 ms·

What an ambitious project, I love it. > Longer-term, bun intends to replace Node.js, Webpack, Babel, yarn, and PostCSS (in production). https://github.com/Jar

What an ambitious project, I love it. > Longer-term, bun intends to replace Node.js, Webpack, Babel, yarn, and PostCSS (in production). https://github.com/Jarred-Sumner/bun#limitations--intended-usage https://github.com/Jarred-Sumner/bun#limitations--intended-u...

wonderbore 4y ago
I love these super-ambitious projects (see Parcel, Rome.js) because after several years they will still fail in many areas at once! > Rome is a formatter, linter, bundler, and more for JavaScript, TypeScript, JSON, HTML, Markdown, and CSS. > Rome is designed to replace Babel, ESLint, webpack, Prettier, Jest, and others. Haven't seen it since. > Parcel: The zero configuration build tool for JavaScript, CSS, HTML, TypeScript, React, images, SASS, SVG, Vue, libraries, Less, CoffeeScript, Node, Stylus, Pug, Electron, Elm, WebGL, extensions, GraphQL, MD As long as you do the bare minimum for each target.
- jokethrowaway 4y ago
  parcel is great, I always use it for personal project and it works pretty well Normally I start with something else (webpack, rollup, whatever happened to be there with the example I'm starting from), then when I hit some roadblocks I just parcel index.html and I have something working.
  - wonderbore 4y ago
    Parcel is great, until it isn’t. I regularly try to switch to Parcel and it’s just impossible on larger projects. If you start with parcel, great! (maybe, as long as you just need to bundle 2 modules and that’s it)
- paulhodge 4y ago
  One of the things that makes frontend dev a nightmare is having to wrangle so many different tools and configurations to build a site, even a simple one. The only next step to improve the situation is all-in-one tools. We're lucky that people are trying to tackle this hard problem.
onion2k 4y ago
Webpack, Babel, yarn, and PostCSS Something has done a bit wrong if you're running any of those tools in production.
- its-dlh 4y ago
  What do you mean? Those are incredibly common tools for production builds.
  - onion2k 4y ago
    You don't use them in production though. Your code is built in a pipeline somewhere using those tools, typically CI/CD, and then the artifacts from that process are what gets deployed to production. If you're actually running Webpack on a production server then you're doing something very unusual.
    - jereees 4y ago
      They are part of the production build pipeline. You need them to have the final product.
      - onion2k 4y ago
        That's not what anyone means when they say "in production" though. When people talk about things being "in production" they mean "on a production server".
        alxndr 4y ago
        So then it's accurate to say that no one uses TypeScript in production??
        whoopdeepoo 4y ago
        You're being absurdly pedantic
        simjnd 4y ago
brundolf 4y ago
Oh that's all, okay, haha.

wonderbore 4y ago

I love these super-ambitious projects (see Parcel, Rome.js) because after several years they will still fail in many areas at once! > Rome is a formatter, linter, bundler, and more for JavaScript, TypeScript, JSON, HTML, Markdown, and CSS. > Rome is designed to replace Babel, ESLint, webpack, Prettier, Jest, and others. Haven't seen it since. > Parcel: The zero configuration build tool for JavaScript, CSS, HTML, TypeScript, React, images, SASS, SVG, Vue, libraries, Less, CoffeeScript, Node, Stylus, Pug, Electron, Elm, WebGL, extensions, GraphQL, MD As long as you do the bare minimum for each target.

jokethrowaway 4y ago
parcel is great, I always use it for personal project and it works pretty well Normally I start with something else (webpack, rollup, whatever happened to be there with the example I'm starting from), then when I hit some roadblocks I just parcel index.html and I have something working.
- wonderbore 4y ago
  Parcel is great, until it isn’t. I regularly try to switch to Parcel and it’s just impossible on larger projects. If you start with parcel, great! (maybe, as long as you just need to bundle 2 modules and that’s it)
paulhodge 4y ago
One of the things that makes frontend dev a nightmare is having to wrangle so many different tools and configurations to build a site, even a simple one. The only next step to improve the situation is all-in-one tools. We're lucky that people are trying to tackle this hard problem.

onion2k 4y ago

Webpack, Babel, yarn, and PostCSS Something has done a bit wrong if you're running any of those tools in production.

its-dlh 4y ago
What do you mean? Those are incredibly common tools for production builds.
- onion2k 4y ago
  You don't use them in production though. Your code is built in a pipeline somewhere using those tools, typically CI/CD, and then the artifacts from that process are what gets deployed to production. If you're actually running Webpack on a production server then you're doing something very unusual.
  - jereees 4y ago
    They are part of the production build pipeline. You need them to have the final product.
    - onion2k 4y ago
      That's not what anyone means when they say "in production" though. When people talk about things being "in production" they mean "on a production server".
      - alxndr 4y ago
        So then it's accurate to say that no one uses TypeScript in production??
      - whoopdeepoo 4y ago
        You're being absurdly pedantic
      - simjnd 4y ago

brundolf 4y ago

Oh that's all, okay, haha.