Skip to content

Conversation

@simonhammes
Copy link
Contributor

What?

Update Typescript to 5.4.5

Testing Instructions

  • CI
  • npm run build locally

@simonhammes simonhammes marked this pull request as ready for review April 17, 2024 19:42
@github-actions
Copy link

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: simonhammes <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Copy link
Member

@jsnajdr jsnajdr left a comment

Choose a reason for hiding this comment

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

Yes, this looks good 👍 I just tried to upgrade TS locally and arrived at exactly the same changes.

@jsnajdr jsnajdr added the [Type] Build Tooling Issues or PRs related to build tooling label Apr 19, 2024
@WordPress WordPress deleted a comment from github-actions bot Apr 19, 2024
"incremental": false,
"composite": false,
"module": "CommonJS",
"module": "Node16",
Copy link
Member

Choose a reason for hiding this comment

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

This needs to be done to fix an error:

error TS5110: Option 'module' must be set to 'Node16' when option 'moduleResolution' is set to 'Node16'.

I'm not really sure what exactly this does. The matching moduleResolution: node16 field was added by @swissspidy in https://github.com/WordPress/gutenberg/pull/52993/files#r1288451752

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Type] Build Tooling Issues or PRs related to build tooling

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants