-
Notifications
You must be signed in to change notification settings - Fork 1
Deprecate events-emitter-es6 for node:events #32
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
Conversation
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.
Do we really need the Yarn changes? If yes, can we skip the yarnrc and gitignore and just use corepack instead?
package.json
Outdated
}, | ||
"packageManager": "[email protected]+sha512.a6b2f7906b721bba3d67d4aff083df04dad64c399707841b7acf00f6b133b7ac24255f2652fa22ae3534329dc6180534e98d17432037ff6fd140556e2bb3137e" | ||
} |
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.
Based on the lockfile changes, seems like you updated to Yarn 4?
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.
But it's not clear because this field is removed?
7608165
to
4970cb1
Compare
Done, apologies for the changes |
sorry, so what version of Yarn is being used? the package json is unchanged |
I left it as is (yarn 1) |
ok, I'll revert the lockfile in a bit as the lockfile is still using the Yarn 3 format |
edc1cc6
to
d401a3c
Compare
this works in the browser? |
Yup, it is |
events-emitter-es6 package was causing TypeScript issues. Anyways, it has not been maintained for 7 years+, and there is now a core node module events.
Note: Will require creating a new release and update the dependency on frontend