Answer the question
In order to leave comments, you need to log in
Why is it taking so long for Angular 2 + TypeScript to be built by webpack?
Our team leader chuckles a little about the fact that his Java application (application server and other instances) is compiled instantly, and what I did on NodeJS (fastened gzip and pre-compressed files I form) takes a very long time (the usual gzip utility through the console instantly generates gzip files), webpack 2 itself in the -minimize-optimize mode collects everything for an overly long time (although there are only one or two files there), I understand Tree Shacking is still declared in webpack 2, but it's wildly long and time-consuming , especially at the time of deployment through Travis CI or TeamCity
What can you think of interesting and useful?
Answer the question
In order to leave comments, you need to log in
Try to use another typescript loader, this one: awesome-typescript-loader , I also had a problem that the typescript took a long time to compile, this seems to have partially corrected the situation
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question