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
Thanks, I think that the problem is that I didn't publish a new version of @babel/proposal-private-methods since it technically didn't have any change, but by doing so the new @babel/preset-env could still depend on the older @babel/helper-create-class-features-plugin version that still had the "Class fields are not enabled" error.
FYI, in case it helps others who end-up there, this change also resulted in us having to explicitly add the @babel/plugin-proposal-class-properties transform to our Babel Config to get things working again (after also hitting the same issue as @lensbart did; thank you @nicolo-ribaudo for the quick turn-around on that one).
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.