-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
build: Fix order for build:dev
command
#8840
Conversation
We actually rely on types being built before transpiling, so we cannot parallelize this - this fails if running this from an unbuilt project.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
huh, I would have thought that lerna would understand this by itself
Hmm, we do not "officially" depend on the types job for the transpile job 🤔 maybe we should actually change this? 🤔 |
Dumb question, why do we rely on types for transpilation? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We actually rely on types being built before transpiling
Hmm this sounds new to me. IIRC we explicitly separated type checking from transpiling to speed things up. Did this change recently? Maybe with the TS upgrade/downleveling?
size-limit report 📦
|
So to reproduce right now: yarn clean:all
yarn build:dev Results (for me) in:
Maybe this is actually more an angular specific problem 🤔 I'll see if I can just fix that! |
Replaced by #8841 |
We actually rely on types being built before transpiling, so we cannot parallelize this - this fails if running this from an unbuilt project.