Closed sethidden closed 5 months ago
Ah it's just yarn's error - it installs on npm but shows warnings about incompatible engine, where it errors on yarn instead.
See also https://github.com/slackapi/bolt-js/issues/2085
Still, for example our package uses contentstack@^3.17.1, so it'll resolve to contentstack@3.19.x if someone else installs it, and it won't work on Node 16 if someone uses yarn
EDIT: https://github.com/slackapi/bolt-js/issues/2085#issuecomment-2033871950 Seems that it's @slack/bolt@3.14.0, not 3.17.1, so reverting to 3.14 would fix it, if you need Node 16 support
Given that bolt is only used in an internal script and not the package runtime, it should be in devDepencies, not dependencies
, no? π
Hello guys, any progress on this one?
Hey @sethidden @bartoszherba , we will be releasing a new version with the fix very soon. I will update here once its released.
@sethidden The fix has been released, please do check.
The usage of @slack/bolt@3.17.1 installs a version that doesn't support Node 16, it was dropped in 3.14.x - https://github.com/slackapi/bolt-js/releases/tag/%40slack%2Fbolt%403.14.0.
On Node 16, this will result in this error:
Please either add the information about dropping Node 16 to the CHANGELOG.md or revert (if you intend for Node 16 to work, not sure if it's a priority for Contentstack)
or maybe add an engines >= field as well