#59078 closed enhancement (fixed)
Update the regenerator-runtime library
| Reported by: | desrosj | Owned by: | desrosj |
|---|---|---|---|
| Priority: | normal | Milestone: | 6.4 |
| Component: | External Libraries | Version: | |
| Severity: | normal | Keywords: | good-first-bug has-patch commit |
| Cc: | Focuses: |
Description
There's a new version of the regenerator-runtime polyfill library (0.14.0).
This library is no longer used directly in Core, but is maintained as a courtesy.
A full list of changes can be found on GitHub: https://github.com/facebook/regenerator/compare/regenerator-runtime%400.13.11...regenerator-runtime%400.14.0.
Change History (6)
This ticket was mentioned in PR #5004 on WordPress/wordpress-develop by @rajinsharwar.
3 years ago
#1
- Keywords has-patch added; needs-patch removed
#2
follow-up:
↓ 4
@
3 years ago
babel/runtime@7.20.13 has regenerator-runtime@0.13.11 as dependency, in order to change regenerator-runtime, babel/runtime needs to be changed as well, otherwise it will still use older version.
#4
in reply to: ↑ 2
@
3 years ago
- Keywords commit added
- Owner set to
- Status new → assigned
Replying to oglekler:
babel/runtime@7.20.13 has regenerator-runtime@0.13.11 as dependency, in order to change regenerator-runtime, babel/runtime needs to be changed as well, otherwise it will still use older version.
Hmm, I did some testing and it seems that the PR attached works great. npm should be smart enough to resolve this.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Updating regenerator-runtime to 0.14.0
Trac ticket: https://core.trac.wordpress.org/ticket/59078