Skip to content
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(tsconfig): use recommendations from @tsconfig/node12 for cjs #3182

Closed
wants to merge 2 commits into from

Conversation

trivikr
Copy link
Member

@trivikr trivikr commented Jan 12, 2022

Issue

Follow-up to #3141
The Node.js 10.x was deprecated, but TSConfig still had ES2018 as a target

Description

Updates target in tsconfig.cjs.json as recommendation from @tsconfig/node12
Refs: https://github.com/tsconfig/bases/blob/main/bases/node12.json

Testing

CI

Additional Context

We can't extend @tsconfig/node12 as Typescript extends doesn't support array.
Refs: microsoft/TypeScript#29118


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@trivikr trivikr requested a review from a team as a code owner January 12, 2022 19:23
"noEmitHelpers": true,
"target": "ES2018",
"target": "es2019",

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

extra line?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wanted to demarcate main key: i.e. lib, module, target from the rest.
We should bump to yarn berry, and put constraints for such and other rules.

Anyway, we can't merge this change as CI is failing, as we define tsconfig.cjs.json for a browser package.
We should write a yarn berry constraints for browser, node, and universal packages and a standardized way for defining runtime specific packages.

@trivikr
Copy link
Member Author

trivikr commented Aug 9, 2023

Closing as this PR was abandoned due to multiple CI failures.

@trivikr trivikr closed this Aug 9, 2023
@trivikr trivikr deleted the tsconfig-node-12 branch August 9, 2023 20:18
@github-actions
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants