-
Notifications
You must be signed in to change notification settings - Fork 395
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
Merge #359 #387 to the @slack/bolt@next branch #393
Merge #359 #387 to the @slack/bolt@next branch #393
Conversation
Codecov Report
@@ Coverage Diff @@
## @slack/bolt@next #393 +/- ##
====================================================
+ Coverage 83.56% 84.09% +0.53%
====================================================
Files 7 7
Lines 505 522 +17
Branches 145 148 +3
====================================================
+ Hits 422 439 +17
Misses 54 54
Partials 29 29
Continue to review full report at Codecov.
|
Hello!! Hey is there a way to point the npm package to this "next" version? Thanks a lot in advance :) |
@juank11memphis This is the way I do it:
From there, navigate to your apps directory (Where you want to use this next version of bolt). Run the following command.
This should make it so you are using your globally linked Let me know if that works for you. |
@juank11memphis if |
Hi @stevengill Thanks a lot, yeah I noticed that this morning, that's awesome news! Thanks also for the npm link advice, now I know how to do this if in the future I need stuff from @next version :) |
Compose middleware resolve conflicts with slackapi#393
Summary
This pull request merges #359 #387 into the
@slack/bolt@next
brach that will be Bolt v2 soon. I've cafelly cherry-picked those commits but I would like to have others' review just in case.Requirements (place an
x
in each[ ]
)