Babel (Formerly 6to5)
XO
Our great sponsors
Babel (Formerly 6to5) | XO | |
---|---|---|
57 | 9 | |
42,844 | 7,523 | |
0.2% | 0.8% | |
9.8 | 6.0 | |
6 days ago | 20 days ago | |
TypeScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Babel (Formerly 6to5)
-
Mastering Jest Configuration for React TypeScript Projects with Vite: A Step-by-Step Guide
node 'node_modules/.bin/jest' '/Users/satparkash/code/test-app/src/A pp.test.tsx' -t 'App' FAIL src/App.test.tsx ● Test suite failed to run SyntaxError: /Users/satparkash/code/test-app/src/App.test.tsx: Support for the experimental syntax 'jsx' isn't currently enabled (6:12): 4 | describe('App', () => { 5 | it('should work as expected', () => { > 6 | render(); | ^ 7 | }); 8 | }); 9 | Add @babel/preset-react (https://github.com/babel/babel/tree/main/packages/babel-preset-react) to the 'presets' section of your Babel config to enable transformation. If you want to leave it as-is, add @babel/plugin-syntax-jsx (https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-jsx) to the 'plugins' section to enable parsing. Test Suites: 1 failed, 1 total Tests: 0 total Snapshots: 0 total Time: 0.278 s Ran all test suites matching /\/Users\/satparkash\/code\/test-app\/src\/App.test.tsx/i with tests matching "App".
- Open source public fund experiment - One and a half years update
-
I Reworked my Rate My GMU Professor (Google Extension)
Webpack (Babel) - https://babel.dev/
-
Babel is used by millions, so why are we running out of money? (2021)
I do appreciate your transparency, though I disagree with the sentiment that I’m arguing from a position of bad faith.
It’s a self-evident fact that the Babel team has not shown a moment of interest in lowering their role in the JavaScript ecosystem to anything short of kingmakers. Have a gander at their GitHub README and what do we see?[1]
- “Babel is a compiler for writing next generation JavaScript.” Indefinitely.
- Over a dozen sponsor logos. An embarrassment of riches.
- A literal audio recording of a song in praise of the project.
The Babel team has a well documented history of their priorities[2], emphasizing the need for a modular approach that has no exit strategy[3]. At best, we have a case of accidental entrenchment and long term dependence on the Babel brewing as early as 2017![4]
Compare this infinite circus to the humble but popular Normalize.css, which has the express purpose to stop existing.[5]
If the Babel team wants to raise some money, they can start by putting a plan together that would codify an exit strategy. It’s certainly more noble than their current plan of barnacling on to every NPM package…
- [1] https://github.com/babel/babel
- [2] https://github.com/babel/notes
- [3] https://github.com/babel/notes/blob/master/2016/2016-07/july...
- [4] https://github.com/babel/notes/blob/master/2017/2017-04/apri...
-
Reveddit does not work
The problem was I had used some new code, Javascript's replaceAll(), that is unsupported by older browsers. And, the setup I have to automatically fix such issues (called babel) is out of date. So, while this problem appears to be resolved there, I hadn't updated that in awhile.
-
The Complete Guide for Setting Up React App from Scratch (feat. TypeScript)
babel-loader(v9.1.0): allows transpiling JavaScript files using Babel and webpack.
-
Upgrade your Lerna Workspace - Make it Fast and Modern!
created 6 years ago to solve the specific problem of managing the Babel repo packages
- “Ignore the f'ing haters ” And other lessons learned from creating a popular
-
React project structure for scale: decomposition, layers and hierarchy
There are quite a few public repositories of well-known projects that use the multi-packages monorepo approach: Babel, React, Jest to name a few.
-
NPM Vulnerability Discussion on Twitter
The reason it doesn't get called out is because the philosophy of "thousands of small packages" has spread far and wide. [1]
For every person calling it out like we're doing here, there are ten others praising maintainers able to whip ten semi-useless packages per week.
It's not just random maintainers making small packages. The core infrastructure of Javascript is in it. Babel is made of hundreds of packages, which all live on the same repository (because of course the maintainers don't want the hassle of maintaining multiple things). Some of those packages don't even have anything of importance in it, just metadata, a couple flags and some boilerplate [2]. The package is just a way of organizing code. Webpack, ESLint and others aren't exactly better.
The reason people do it is because other popular people have been doing it for a long time, and nobody calls them out on it.
[1] https://blog.sindresorhus.com/small-focused-modules-9238d977...
[1] https://github.com/babel/babel/blob/main/packages/babel-plug...
XO
-
ESLint: Flat Config Rollout Plan
Usually you would pick a config you like and set it up for your project, notable ones are already mentioned but I'll mention more:
-
Configuring ESLint, Prettier, and TypeScript Together | Josh Goldberg
You might enjoy `xo` :) https://github.com/xojs/xo
- From Ruby to Node: Overhauling Shopify’s CLI for a Better Developer Experience
-
Front-end Guide
XO
-
Code Review chronicles: destructuring, linting and one valid reason for Typescript
The developer told me we could not do that because the linter we are using. (XO)[https://github.com/xojs/xo] started complaining.
-
Yarn.lock: How to Update it
Real world example: you are using create-react-app, and you want to also to use xo, as both come with their own version of ESLint pre-installed, you could end up with 2 ESLint installed.
-
Lint rules updates: a sane and safe approach to fixes
One of the biggest hassles to update was the linter we are using: XO, which is a very opinionated, but customizable linter base on ESlint.
-
JavaScript Influencers to Follow in 2021🤩
Projects: awesome, awesome-nodejs, avajs/ava, xojs/xo
What are some alternatives?
Standard - 🌟 JavaScript Style Guide, with linter & automatic code fixer
ESLint - Find and fix problems in your JavaScript code.
Traceur compiler - Traceur is a JavaScript.next-to-JavaScript-of-today compiler
Live Server - A simple development http server with live reload capability.
Lebab - Turn your ES5 code into readable ES6. Lebab does the opposite of what Babel does.
torrent - download torrents with node from the CLI
dark-mode - Control the macOS dark mode from the command-line
ECMAScript 6 compatibility table - ECMAScript compatibility tables
swc - Rust-based platform for the Web
http-server - a simple zero-configuration command-line http server
es6-features - ECMAScript 6: Feature Overview & Comparison