babel-sublime VS awesome-emacs

GitHub | Website

Some of the most popular JavaScript linting tools are ESLint, JSHint, JSLint and JSCS. We're going to be using ESLint. It’s very flexible, easy to use and has the best ES6 support, which will be helpful if we introduce more modern JavaScript (that will be transpiled for older browsers using https://babeljs.io/). All rules for ESLint can be found here: https://eslint.org/docs/rules/.

This simply extends the existing build process that many front-end frameworks have. After Babel's done with its transpilation, it merely executes code to compile your initial screen into static HTML and CSS. This isn't entirely dissimilar from how SSR hydrates your initial screen, but it's done at compile-time, not at request time.

First, we switched the default compiler for new projects from Babel to SWC (Speedy Web Compiler). SWC is dramatically faster than Babel and requires zero configuration. We’ll continue to support Babel in any project currently using it.

Nuxt.js is an open-source JavaScript framework built on Vue.js, Node.js, Vite, and Babel.js used for creating fast, cutting-edge applications. Nuxt.js possesses similar features to Next.js, with the major difference being the web framework it is compatible with. Next.js is a React framework whereas Nuxt.js is a Vue framework.

Disclaimer: If you've already developed Babel or ESLint plugins, this article may not be as beneficial for you, as you're likely already familiar with the majority of the content covered here.

Preprocessors: SSGs leverage preprocessors to streamline the development process. Preprocessors like SASS for CSS or Babel for JavaScript offer additional features and simplify code development.

To transpile our code, we will use Babel - a JavaScript compiler, that will generate files Node.js is happy with, and Webpack - a JavaScript bundler, that will bundle our code and automate the compilation step.

Can be used with promises, Node-style callbacks, ES6 generators and async/await (using Babel).

Growth in Tooling: Tools like Babel allowed developers to use the latest JavaScript features without waiting for Node.js support, while Webpack streamlined bundling and module loading.

“A community driven list of useful Emacs packages, libraries and other items.” https://github.com/emacs-tw/awesome-emacs

I've used emacs for about the same (started with microemacs in the 80s). I also had an extremely crufty init.el and recently decided to start over. I compared 19 emacs distributions (from this list and this r/emacs post). I looked at

But, to be honest, I think it simply is not for everyone. But sure one thing is lacking (as far as I know): a metatutorial. Like a big "chart" telling people what can be done with Emacs (with a few examples), something like https://github.com/emacs-tw/awesome-emacs for newcomers.

Awesome-emqcs is a great resource for knowing what packages are there: https://github.com/emacs-tw/awesome-emacs

For packages, Checking what people in the community commonly use, such as in https://github.com/emacs-tw/awesome-emacs/ or checking packages for review in Doom Emacs helps a lot in selection. There are also great guides, such as Kristoffer Balintona's https://kristofferbalintona.me/categories/guides/. Personally, my bias in selecting packagges is towards the ones that integrate well with built-in Emacs functionalities. I could provide you a list if you want.

Take it slowly, check some packages that seem like they might be useful to you: (check https://github.com/emacs-tw/awesome-emacs out for example).

Awesome Emacs for utility-oriented packages

Awesome Emacs, a community driven list of useful Emacs packages, utilities and libraries