Oh this would be such a good fit for my dream of serving federated backend code from web readable hosting https://webcode.run/. - Source: Hacker News / 10 months ago

This would be so amazing. In order to access most vanilla services like redis, postgres etc. You need to deploy a bridge https://github.com/zquestz/ws-tcp-proxy -- somewhat abandoned at this point but it is still running), and a big problem with the approach was the web's inability to make TCP connections. - Source: Hacker News / over 1 year ago

Yeah, you are right. I made https://webcode.run also for this reason (also hot code reload and debugging but for JavaScript computational notebooks). - Source: Hacker News / almost 2 years ago

This was why I created https://webcode.run the elimination of all tooling and a fast development loop even for backend. - Source: Hacker News / almost 2 years ago

I am building a compute layer for Observablehq which enables services to brought up using nothing other than a web browser. It's a bit too soon to call it a K8s replacement but the motivation was the complexity and laggyness of bringing up services on cloud or k8s. The WEB + on demand infrastructure is the distributed replacement of K8S https://webcode.run/ WEBCode is about eliminating environments and the... - Source: Hacker News / over 2 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 / 3 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 / 4 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 / 4 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 / 6 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 / 9 months ago