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
chore(deps): bump dependencies #263
Conversation
49df31b
to
01b730b
Compare
- update eslint to latest node@10 compatible version - add explicit minimist version - update prettier version & fix code format
43363fc
to
53795ce
Compare
- update minimatch & path-parse transitive dependencies in lock file - update eslint-plugin-jest - regenerate snapshots
53795ce
to
bc44f98
Compare
Version updates:
|
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.
Can we update master
to even higher versions? I don't think that sticking to node@10 is a hard requirement. We can document it in the migration guide and release version 3.0 to emphasize this change.
Patches of XTaC 2.3 and 2.2 should probably stick to node@10.
chalk ^4.1.2 → ^5.1.2
got ^11.8.5 → ^12.5.2
eslint ^7.32.0 → ^8.26.0
eslint-config-prettier 8.3.0 → 8.5.0
eslint-plugin-bpmn-io ^0.14.1 → ^0.16.0
jest ^27.5.1 → ^29.2.2
Of course, we can. For the non cjs dependencies (got, chalk) we have to either introduce some transpiling or we can convert our client to esm, too. |
I'm okay with switching to ESM for |
Created a separate issue for the final dependency & ESM updates: camunda/camunda-bpm-platform#2881 |
related to camunda/camunda-bpm-platform#2801