fork-ts-checker-webpack-plugin
swc
Our great sponsors
fork-ts-checker-webpack-plugin | swc | |
---|---|---|
8 | 139 | |
1,918 | 29,952 | |
0.9% | 1.2% | |
5.2 | 9.9 | |
14 days ago | 6 days 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.
fork-ts-checker-webpack-plugin
-
Converting to Typescript
Okay. The normal setup is that you use https://github.com/TypeStrong/ts-loader or https://github.com/TypeStrong/fork-ts-checker-webpack-plugin as part of your Webpack config. Those will run the TS compilation step as part of the Webpack processing sequence.
-
Announcing Parcel CSS: A new CSS parser, compiler, and minifier written in Rust!
I work on a TypeScript project of similar size and complexity, and ours does not take even nearly that long to compile on save. Have you tried fork-ts-checker-webpack-plugin? We had compile times similar to yours until we started using it. Went from >60s to <1s builds in development. It's very simple to set up.
-
Do you guys compile with ts-loader or babel-loader?
Yeah, I mean less loaders = less time. Did you try fork ts checker and compileOnly? https://github.com/TypeStrong/fork-ts-checker-webpack-plugin
-
Hey when I want to run a vue frontend I need to increase my memory size, because js jumps out of memory.
That worker/memory limit is for the type checking only (rather than runtime memory), I believe this is done using https://github.com/TypeStrong/fork-ts-checker-webpack-plugin
-
Adding Typescript to your Existing Rails App
There are many ways to integrate TypeScript with an existing Webpack configuration. If you use the babel-loader package to transpile JavaScript files, you can add the @babel/preset-typescript preset to generate JavaScript files and the Fork TS Checker Webpack Plugin package to run the TypeScript type checker so that the build fails if there are type errors.
-
Blazing fast TypeScript with Webpack and ESBuild
esbuild-loader (secret sauce!) fork-ts-checker-webpack-plugin (helps us with typechecking) nodemon-webpack-plugin (We can also use webpack-dev-server)
-
Debugging with developer tools
I cloned github repo into a new dir, ran install with --frozen-lockfile and test-gui with --clean and got the same error. Looks like it's coming from fork-ts-checker-webpack-plugin and then found this among its reported issues: (https://github.com/TypeStrong/fork-ts-checker-webpack-plugin/issues/562).
-
Why Is Esbuild Fast?
You may want to check out this webpack plugin [1], though I'm not sure how much it could get you there.
[1] https://github.com/TypeStrong/fork-ts-checker-webpack-plugin...
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?
babel-loader - 📦 Babel loader for webpack
esbuild - An extremely fast bundler for the web
webpack-dev-server - Serves a webpack app. Updates the browser on changes. Documentation https://webpack.js.org/configuration/dev-server/.
vite - Next generation frontend tooling. It's fast!
esbuild
ts-loader - TypeScript loader for webpack
sucrase - Super-fast alternative to Babel for when you can target modern JS runtimes
tsup - The simplest and fastest way to bundle your TypeScript libraries.
vite-ts-tailwind-starter - Opinionated Vite + Vue 3 + TypeScript + Tailwind CSS starter template w/ tests and CI.
vitest - Next generation testing framework powered by Vite.
esbuild-register - Transpile JSX, TypeScript and esnext features on the fly with esbuild
ts-node - TypeScript execution and REPL for node.js