Skip to content

Conversation

@gabmontes
Copy link
Member

The property resolver in promise-mem is optional! This silly bug was causing TS errors to show up.

Process checklist

  • Manual tests passed or not applicable.
  • Automated tests added or not applicable.
  • Documentation updated or not required.

Metrics

Actual effort: 0.5h

@gabmontes gabmontes self-assigned this Jun 17, 2025
@gabmontes gabmontes marked this pull request as ready for review June 17, 2025 21:55
@gabmontes gabmontes enabled auto-merge June 17, 2025 21:55
Copy link
Contributor

@gndelia gndelia left a comment

Choose a reason for hiding this comment

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

Shouldn't the root's lockfile be updated due to the version update? It seems to me that a npm i was missing after (manually?) updating the version in the package.json 🤔

@gabmontes
Copy link
Member Author

@gndelia I don't think that was needed but I just updated the lockfile anyway.

@gabmontes gabmontes requested a review from gndelia June 17, 2025 23:59
@gndelia
Copy link
Contributor

gndelia commented Jun 18, 2025

@gndelia I don't think that was needed but I just updated the lockfile anyway.

true, but the next time someone run a npm i they will see changes appear in the lockfile, so better commit them now 😄

@gabmontes gabmontes merged commit 10a8383 into master Jun 18, 2025
5 of 6 checks passed
@gabmontes gabmontes deleted the fix-promise-mem-types branch June 18, 2025 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants