-
Notifications
You must be signed in to change notification settings - Fork 1
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
chore: Extending "@guardian/tsconfig" in tsconfig #838
Conversation
🦋 Changeset detectedLatest commit: 9be4825 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
cdk/tsconfig.json
Outdated
"outDir": "dist", | ||
"allowJs": true, | ||
"isolatedModules": true, | ||
"module": "ES6", |
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.
do you need this value specifically? the default from the config is esnext
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've removed the module from this tsconfig.json file. However, I had to add the "module": "commonjs" to monitoring/tsconfig.json
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.
Looks good!
I believe this has produced an invalid output for the types, as this version of the library fails to compile with TypeScript in frontend: guardian/frontend#26680 It seems like the Consent State object is now typed as |
What does this change?
As recommended by Joe Cowton, I've installed "@guardian/tsconfig" and extended it in the tsconfig.json.
Why?
To ensure that CMP linting standards align with the patterns recommended Client Side