pretty-ts-errors
swc
pretty-ts-errors | swc | |
---|---|---|
13 | 140 | |
12,251 | 30,118 | |
- | 0.9% | |
6.3 | 9.9 | |
10 days ago | about 2 hours ago | |
TypeScript | Rust | |
MIT License | Apache License 2.0 |
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.
pretty-ts-errors
-
What is JSDoc and why you may not need typescript for your next project?
Besides the features TypeScript itself proposed, the most important thing it brought to the community was the ability to create cool features around this compiler that enhance the developer experience and productivity. Tools like tsserver, pretty ts errors, and many others are actively improving the ecosystem for both JavaScript and TypeScript writers.
-
Home made plugin - Better formatted TypeScript error messages
Being heavily inspired by VSCode plugin for prettifying TS error messages, I decided to try and create similar as Neovim plugin.
-
How to make type safe a function that receives a prisma.[modelName] ?
#1: VSCode extension that makes TypeScript errors prettier and human-readable | 28 comments #2: Those who know, know... | 63 comments #3: Announcing TypeScript 5.0 Beta | 24 comments
- How do I fix this Type error: No overload matches this call.
- Pretty TypeScript Errors VSCode Plugin
- [Neovim] Plugin assez erreurs comme celui-ci?
-
TS Formatted Errors
Is there anything similar to this project for neovim: https://github.com/yoavbls/pretty-ts-errors
- Pretty TypeScript Errors – Make TypeScript Errors Human-Readable in VSCode
-
VSCode extension that makes TypeScript errors prettier and human-readable
It is already reported though: https://github.com/yoavbls/pretty-ts-errors/issues/3
- Pretty errors plugin like this?
swc
-
Storybook 8 Beta
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.
-
What is JSDoc and why you may not need typescript for your next project?
SWC
-
Implementing auth flow as fast as possible using NestJS
As the reference explains “**SWC** (Speedy Web Compiler) is an extensible Rust-based platform that can be used for both compilation and bundling. Using SWC with Nest CLI is a great and simple way to significantly speed up your development process.”
-
Ruby Outperforms C: Breaking the Catch-22
This is specifically about breaking the myth that performing expensive self-contained operations (e.g, parsing GraphQL) in a native extension (C, Rust, etc.) is always faster than the interpreted language.
The JS ecosystem has the same problem, people think rewriting everything in Rust will be a magic fix. In practice, there's always the problem highlighted in the post (transitioning is expensive, causes optimization bailouts), as well as the cost of actually getting the results back into Node-land. This is why SWC abandoned the JS API for writing plugins - constantly bouncing back and forth while traversing AST nodes was even slower than Babel (e.g https://github.com/swc-project/swc/issues/1392#issuecomment-...)
-
Building a Minimalist Docker Image with Node, TypeScript
Why Speedy Web Compiler ?
- TypeScript Is Surprisingly OK for Compilers
- Speedy Web Compiler: Rust-Based Platform for the Web
-
FTA: Fast TypeScript Analyzer
FTA is a TypeScript static analysis tool built on the speedy foundations of swc. FTA is fast; capable of analyzing more than 150 files per second on typical hardware, it offers a powerful addition to your code quality toolkit.
-
Show HN: Ezno, a TypeScript checker written in Rust, is now open source
Very cool! I'm curious, is this intended for dev tooling?
For example, I could see this (or something similar) being useful as the engine for a typescript language server that would be faster than the standard one
But if it's not aimed at 1:1 with tsc, would it be intended more for something like swc[1]?
Or what would you expect people to use this for, besides just being a cool project to learn from?
[1] https://github.com/swc-project/swc
-
TypeScript team released an explorer for performance tuning
This is... good news, but I still cannot fathom using the default Typescript compiler for regular development. Seriously, leave the type-checking to your IDE and CICD chain, and switch to using tsx (https://www.npmjs.com/package/tsx) or swc (https://swc.rs/) and you will _immediately_ notice the difference in speed and productivity.
What are some alternatives?
format-ts-errors.nvim - Neovim plugin to format tsserver LSP errors
esbuild - An extremely fast bundler for the web
pretty_hover - A small and customizable neovim plugin for pretty printing the hover information from LSP servers
vite - Next generation frontend tooling. It's fast!
hover.nvim - Hover plugin framework for Neovim
ts-loader - TypeScript loader for webpack
markmap-vscode - Integrate markmap into VSCode
tsup - The simplest and fastest way to bundle your TypeScript libraries.
vscode-ibmi - 🌍 IBM i development extension for VS Code
vitest - Next generation testing framework powered by Vite.
diagnostic-window.nvim - Shows diagnostic messages in a separate window, which is particularly helpful for long message like those seen in typescript.
ts-node - TypeScript execution and REPL for node.js