Hammer.js VS Babel

Actually, I thought if I used hammerjs, it would be easy, but actually I gave up using that since it seemed that hammerjs's development wasn't active any more unfortunately. - Source: dev.to / over 1 year ago

Looking at https://delassus.com/javascripts/app.js you can see they used hammer.js(https://hammerjs.github.io/) to achieve the gestures, which I am assuming is your focus here. Source: over 2 years ago

Hammer.js is a library and gives you the ability to add touch gestures on websites. It means it can recognize & track gestures performed by the fingers and mouse of the user and make animations and all that cool stuff. And you can know the steps on their website here. Source: almost 3 years ago

I had no idea how bad listening for things like key presses and dragging events are today. Given how nice and fairly standard a lot of the APIs across browsers and platforms have become, I was shocked at how rough this space is. I think if I had to do this again, this will be one area where I defer to a library (like hammer.js). - Source: dev.to / about 3 years ago

Maybe something using HammerJS would make it cleaner if you're using a vanilla solution right now? https://hammerjs.github.io/. Source: about 3 years ago

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/. - Source: dev.to / about 2 months ago

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. - Source: dev.to / 2 months ago

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. - Source: dev.to / 3 months ago

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. - Source: dev.to / 5 months ago

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. - Source: dev.to / 7 months ago