Conversation
|
@vlad-zhukov I think I just decreased build time from >20min to ~5min 😀 |
yarn.lock
Outdated
| resolved "https://registry.yarnpkg.com/@types/react/-/react-15.6.15.tgz#1856f932120311aa566f91e6d0c6e613d6448236" | ||
|
|
||
| "@webpack-blocks/elm@^1.0.0": | ||
| version "1.0.0" |
There was a problem hiding this comment.
Where did it come from? It shouldn't be here.
There was a problem hiding this comment.
I was wondering the same, it came up after I ran yarn remove elm elm-hot-loader elm-webpack-loader within ./packages/webpack
EDIT: I forgot to remove @webpack-blocks/elm from devDependencies, good catch!
You can find it here: https://github.com/webpack-blocks/elm
zcei
force-pushed
the
refactor/move-elm-to-own-repo
branch
from
13abf6d to
9902167
Compare
This is awesome! 🏆 I was waiting for this for a long time, finally we can get rid of builds that take forever! P.S. 🤓 technically builds run simultaneously so from 12-15 mins to 2-3, which is even better! |
There was a problem hiding this comment.
I love it! This is another prove why moving elm block to its own repo is the right decision and very healthy for the project overall. Thank you very much, @zcei, of taking care of it!
I'd merge it right away, just want others to see this too! @andywer @jvanbruegge @dmitmel @farism
|
Awesome! |
|
The built time is quite amazing |
|
If elm was experiencing slow build times, it may have been due to invalid reporting of cores to the elm compiler which severely slows down the compiling of modules elm/compiler#1473 |
| - [babel](./packages/babel) | ||
| - [dev-server](./packages/dev-server) | ||
| - [elm](./packages/elm) | ||
| - [elm](https://github.com/webpack-blocks/elm) |
You can find it here: https://github.com/webpack-blocks/elm
You can find it here: https://github.com/webpack-blocks/elm
6 participants
You can find it here: webpack-blocks/elm
Related PR with the e2e test: webpack-blocks/elm#1