babel-sublime VS parcel

18. Babel

@vitejs/plugin-react uses Babel for Fast Refresh

For new and incompatible syntax, the solution is transpiling—converting newer JS syntax to older syntax that can run on older engines. The most popular transpiler? Babel. This process ensures modern JS code can still reach a wide audience, even on legacy systems.

Website: babeljs.io

Fortunately we have tools like PostCSS and Babel, that let you target your specific Browser version, and they'll do their best to transpile and polyfill your code to work with that version. This alone will do a lot of the heavy lifting for you if you are working with a lot of code. However, if you are just writing out a few HTML, CSS, and JS files, then that would be overkill and you can just figure out what code to use by consulting CanIUse.com.

Cross-Browser Compatibility: Some features worked differently across browsers. I used Babel to transpile my JavaScript code, ensuring it worked consistently everywhere.

SuiteScript 2.1 introduces new language features, such as arrow functions and block-scoped variables, which support modern server-side code. However, developers must ensure browser compatibility. Not all browsers support these features natively. Transpilation, using tools like Babel, can convert modern JavaScript to a more compatible version. This ensures scripts run smoothly across different environments.

# React + Vite This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules. Currently, two official plugins are available: - [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/README.md) uses [Babel](https://babeljs.io/) for Fast Refresh - [@vitejs/plugin-react-swc](https://github.com/vitejs/vite-plugin-react-swc) uses [SWC](https://swc.rs/) for Fast Refresh # Fresh-Starts

Babel was one of the first to do this job, developed using JS, with a rich ecosystem and plugins, and has long been integrated into packaging tools such as webpack rollup.

@vitejs/plugin-react uses Babel for Fast Refresh

Parcel is another alternative that requires zero configuration and is super fast. If you want a simple React setup without any hassle, Parcel is a great choice.

From its documentation [1] it looks a lot like a parceljs replacement [2], i.e. a zero config bundler which processes and bundles the dependencies in .html pages. So great for simple websites, not for replacing an entire Vite stack.

[1] https://bun.sh/docs/bundler/fullstack

[2] https://parceljs.org

Packagers are the ones we most frequently come into contact with, such as Webpack Vite and Parcel. The latter may not be commonly used, but it is also a well-established tool.

npm packages dramatically sped up the productivity of developers by being able to leverage other developers' work. However, it had a major disadvantage: cjs was not compatible with web browsers. To solve this problem, the concept of bundlers was born. browserify was the first bundler which essentially worked by traversing an entry point and "bundling" all the require()-ed code into a single .js file compatible with web browsers. As time went on, other bundlers with additional features and differentiators were introduced. Most notably webpack, parcel, rollup, esbuild and vite (in chronological order).

The AI Framework Debate

You will need a web bundler. You can use parcel.js

To run this script, we need a web bundler like parcel js.

Official Website

Someone even opened a discussion to ask if Parcel is dead. The official answer is no, Parcel is still alive, but it's in a we-are-working-on-a-large-refactor-and-no-time-for-minor-releases state. To us, it's like a "duck death": The latest version we can use is from more than a year ago, and we don't know when the next version will be released. It looks like it's dead, it acts like it's dead, so it's dead to us. Trust me, we tried.