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

fix(multiple): use cross-compatible type for setTimeout #30073

Merged
merged 1 commit into from
Nov 25, 2024

Conversation

crisbeto
Copy link
Member

Fixes that some places were raising an error due to the return type of setTimeout being different between the browser and Node.

Fixes that some places were raising an error due to the return type of `setTimeout` being different between the browser and Node.
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Nov 24, 2024
@crisbeto crisbeto requested a review from a team as a code owner November 24, 2024 11:53
@crisbeto crisbeto requested review from mmalerba, andrewseguin and devversion and removed request for a team November 24, 2024 11:53
@devversion
Copy link
Member

It's probably a bug if @types/node leaks into those source files; but this change still LGTM

@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Nov 25, 2024
@crisbeto crisbeto merged commit 26a817c into angular:main Nov 25, 2024
21 of 24 checks passed
crisbeto added a commit that referenced this pull request Nov 25, 2024
Fixes that some places were raising an error due to the return type of `setTimeout` being different between the browser and Node.

(cherry picked from commit 26a817c)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Dec 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants