-
Notifications
You must be signed in to change notification settings - Fork 405
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: add typescript project references #4055
Conversation
as it has issues with the tsconfig used by tsc build with project ref
Failing with various flavours of the following error - Need to debug/fix
|
"noImplicitAny": false, | ||
// Generating Type Definitions from Javascript is blocked by requiring private name | ||
// https://github.com/microsoft/TypeScript/issues/37832 | ||
// "allowJs": true, // for the beautify js files |
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.
would we ever uncomment this?
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.
There are about a half-dozen failures in a couple of packages due to this check. So yes if we can clean them up we can have this enabled. Another way is to have this only in the packages that are failing and have it enabled globally.
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.
Created a WI and linked
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.
Sorry misread as question about noUnusedLocals
in the tsconfig common json.
For allowJs
guess as long as we have the beautify JS src files checked in (not sure if there is a third party lib that can be imported instead that has been created since) and the TSC issue is open. This is in case someone wonders why are the JS files being copied over instead of being run through tsc. Updated comment.
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.
Great work! I didn't QE with changes (well I did a compile before the last set of commits), but this seems like a build task so if it build it builds. If there are any steps required for local dev for this to start working you might call it out in slack after it merges.
@gbockus-sf If/when you have a moment can you please review the recent (mostly doc) changes. |
Extension sizes using https://github.com/lcampos/circleci-to-vscode
Comparing with VSIX files from a recent build on develop it can be noticed that the size hasn't changed significantly
|
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.
Great work
regenerate package lock file to fix merge conflicts
What does this PR do?
extends
correctly (Project References won't work if extends config file TypeStrong/ts-loader#1035)What does this PR doesn't do?
What issues does this PR fix or reference?
@ W-10706475@
Functionality Before
Typescript project config was duplicated per package with no reuse and no references.
Functionality After
Typescript project configs are reused with a common config and project references have been added.
QA Notes