babel-loader
fork-ts-checker-webpack-plugin
babel-loader | fork-ts-checker-webpack-plugin | |
---|---|---|
6 | 8 | |
4,798 | 1,918 | |
0.0% | 0.4% | |
3.9 | 5.2 | |
25 days ago | 25 days ago | |
JavaScript | TypeScript | |
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-loader
-
A webpack.config.js for WordPress Projects
babel-loader
-
Why does Object.assign() require a polyfill when babel-loader is being used?
Uncaught TypeError: Object.assign is not a function I'm already using babel-loader to transpile ES6 to ES5, so all my other ES6 code is working. Yet, Object.assign() only works after I also import "babel-core/polyfill" in my codebase. I see that I can also fix this by importing babel-runtime, but I'd like to understand why Object.assign() requires more than what babel-loader performs — shouldn't babel-loader preprocess everything, including Object.assign()?
-
NPM build error: You may need an appropriate loader to handle this file type
It looks like this may be an old version of webpack according to [this GitHub issue](https://github.com/babel/babel-loader/issues/798).
-
[ES6 modules] Is writing index.ts files for re-exports actually kind of a bad idea in non-published projects?
And babel/webpack seems to get upset at re-exporting things that don't exist at runtime (types and interfaces): https://github.com/babel/babel-loader/issues/603. So, you need to be careful to re-export your types with a different syntax, which is hard to remember when you're writing a file full of export * from 'foo'.
-
I can't get babel to work with react-testing library and nextjs
Apparently, this is usually a problem with Babel 7 and plugins but I've upgraded the plugins and still have this issue: https://github.com/babel/babel-loader/issues/560
-
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.
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...
What are some alternatives?
eslint-loader - [DEPRECATED] A ESlint loader for webpack
swc - Rust-based platform for the Web
Visual Studio Code - Visual Studio Code
webpack-dev-server - Serves a webpack app. Updates the browser on changes. Documentation https://webpack.js.org/configuration/dev-server/.
css-loader - CSS Loader
esbuild
base-wp-theme - Base WP Theme is a starter WordPress theme to use as a base to build WordPress themes from scratch.
sucrase - Super-fast alternative to Babel for when you can target modern JS runtimes
TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
vite-ts-tailwind-starter - Opinionated Vite + Vue 3 + TypeScript + Tailwind CSS starter template w/ tests and CI.
lodash - A modern JavaScript utility library delivering modularity, performance, & extras.
esbuild-register - Transpile JSX, TypeScript and esnext features on the fly with esbuild