Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dev/build: TypeScript WebPack "loader" is old and abandonned project #1097

Closed
danielweck opened this issue Jun 12, 2020 · 3 comments
Closed
Assignees

Comments

@danielweck
Copy link
Member

Archived repo, 200+ open issues:

https://github.com/s-panferov/awesome-typescript-loader

... probably slow(er) too:

s-panferov/awesome-typescript-loader#497 (comment)

... apparently slower than ts-loader which is an active project, and which can be configured with transpileOnly (for even faster compilation times) and with type-checking in separate process:

https://github.com/TypeStrong/ts-loader#transpileonly

https://github.com/TypeStrong/fork-ts-checker-webpack-plugin

I am testing ...

@danielweck danielweck self-assigned this Jun 12, 2020
@danielweck
Copy link
Member Author


ts-loader with transpileOnly and fork-ts-checker-webpack-plugin:

npm run clean && time npm run build
=>

  • npm run build 130.45s user 5.53s system 505% cpu 26.893 total
  • npm run build 124.32s user 4.91s system 499% cpu 25.883 total
  • npm run build 123.74s user 4.75s system 506% cpu 25.392 total
  • npm run build 123.15s user 4.82s system 503% cpu 25.435 total
  • npm run build 121.86s user 4.72s system 502% cpu 25.204 total

ts-loader with transpileOnly and NO fork-ts-checker-webpack-plugin:

npm run clean && time npm run build
=>

  • npm run build 19.70s user 1.58s system 158% cpu 13.444 total
  • npm run build 20.20s user 1.40s system 172% cpu 12.540 total
  • npm run build 19.73s user 1.41s system 168% cpu 12.575 total
  • npm run build 19.50s user 1.39s system 167% cpu 12.468 total

@danielweck
Copy link
Member Author


awesome-typescript-loader with transpileOnly and fork-ts-checker-webpack-plugin:

npm run clean && time npm run build
=>

  • npm run build 145.48s user 6.18s system 523% cpu 28.962 total
  • npm run build 143.93s user 5.63s system 536% cpu 27.863 total
  • npm run build 139.61s user 5.84s system 528% cpu 27.544 total
  • npm run build 140.77s user 5.98s system 528% cpu 27.784 total

awesome-typescript-loader with transpileOnly and NO fork-ts-checker-webpack-plugin:

npm run clean && time npm run build
=>

  • npm run build 31.43s user 2.47s system 152% cpu 22.160 total
  • npm run build 30.74s user 2.27s system 153% cpu 21.505 total
  • npm run build 30.47s user 2.26s system 155% cpu 21.081 total
  • npm run build 31.45s user 2.24s system 157% cpu 21.416 total

@danielweck
Copy link
Member Author

danielweck commented Jun 12, 2020

  1. export SKIP_CHECK_TYPESCRIPT=1
  2. npm run start:dev
  3. enjoy :)

(note that production builds ALWAYS execute the TypeScript compiler to check types, i.e. npm run build npm run start npm run package:[win|mac|linux])

unset SKIP_CHECK_TYPESCRIPT to restore default behaviour, or export SKIP_CHECK_TYPESCRIPT=0 (anything other than 1)

danielweck added a commit that referenced this issue Jun 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant