You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
Has this been released? I'm still seeing "cheerio": "^1.0.0-rc.3", in the enzyme package.json in my node_modules on 3.11.0? or is npm 8 converting = to ^ ?
The reason will be displayed to describe this comment to others. Learn more.
kk, I found this because over the last week cheerio added an exports map, and attempts to require into the module's undeclared files now fail... I worked around it locally by pinning cheerio to rc3 in my project's package.json
The reason will be displayed to describe this comment to others. Learn more.
@Alevale it's already on main, there's no need to cherry-pick anything. It's just that enzyme hasn't yet had a release since before this commit landed.
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Alevale π
Do you have an ETA about his one? How many time it takes in general to release?
It's pretty urgent for us, we have an organisation with a lot of packages and we are actually in a situation where we are adding:
"overrides": {
"cheerio": "1.0.0-rc.3"
}
to all our package.json π. Because of the stable release of cheerio to 1.0.0 that happened last week.
cafdb2b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Has this been released? I'm still seeing
"cheerio": "^1.0.0-rc.3",
in the enzyme package.json in my node_modules on 3.11.0? or is npm 8 converting=
to^
?cafdb2b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, this hasn't been released.
cafdb2b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
kk, I found this because over the last week cheerio added an exports map, and attempts to require into the module's undeclared files now fail... I worked around it locally by pinning cheerio to rc3 in my project's package.json
cafdb2b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ljharb could we cherry pick this by any chance? It would fix #2607 AFAIK
Out of curiosity, why wasn't this picked into the package?
cafdb2b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Alevale it's already on main, there's no need to cherry-pick anything. It's just that
enzyme
hasn't yet had a release since before this commit landed.cafdb2b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to release a patch to get this one?
cafdb2b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Alevale π
Do you have an ETA about his one? How many time it takes in general to release?
It's pretty urgent for us, we have an organisation with a lot of packages and we are actually in a situation where we are adding:
to all our
package.json
π. Because of the stable release of cheerio to 1.0.0 that happened last week.cafdb2b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@raphaelboukara unfortunately/fortunately I am not an owner nor maintainer for any of those packages, I'm just another affected user π’