-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Use ts-node for v0 scripts and remove docs alias #12789
Conversation
tsNode.register({ dir: __dirname }); | ||
tsNode.register({ | ||
dir: __dirname, | ||
transpileOnly: true, |
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.
So we will not have any benefits from type checks? Am I correct?
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.
I can turn on type checks if you want, I was just concerned about regressing build perf.
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.
In general I like type checks aside from the perf concerns :)
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.
Turned off type checking again due to perf concerns...nearly 30s per project for clean
!! 😬
Asset size changesSize Auditor did not detect a change in bundle size for any component! Baseline commit: 9f4e4375ed8dedc134aecfbfa618a662d512e75b (build) |
Perf AnalysisNo significant results to display. All results
Perf Analysis (Fluent)Potential regressions comparing to master
Perf comparison
Perf tests with no regressions
|
Note in case anyone else wants to try it, I've been testing perf with this absurdly long command intended to target only the projects still using gulp: Running Note that both |
There may also be issues with how ts-node handles output, at least the way that gulp does it. With gulp-based tasks, it shows all the output at once rather than as it comes. I haven't noticed this problem in the just-based tasks which also use ts-node, so not sure what's going on there. |
7c6cd49
to
c1eb5c0
Compare
Switch v0 scripts from using
@babel/register
tots-node
. This is a minor step in converging scripts.Remove remaining
docs
aliases from v0 code.I had to downgrade
ts-node
to version 7 because version 8 disables caching, and the perf without caching is abysmal (~30s/project forclean
!). I also turned off type checking for perf reasons. While downgrading to the version with caching does involve some risk of cache-related issues, I've definitely seen similar issues with @babel/register especially while changing build scripts (unfortunately never pinned down repro steps), so switching to ts-node probably preserves a similar level of risk.Microsoft Reviewers: Open in CodeFlow