Basic initialization of Bolt fails on RunKit

[brianjychan]

Description

Today I began seeing the error:
Error: Cannot find module '/app/available_modules/1635904312000/@slack/bolt/dist/index.js'. Please verify that the package.json has a valid "main" entry

What type of issue is this? (place an x in one of the [ ])

• bug
• enhancement (feature request)
• question
• documentation related
• example code related
• testing related
• discussion

Requirements (place an x in each of the [ ])

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

---

Bug Report

Filling out the following details about bugs will help us solve your issue sooner.

Reproducible in:

package version: 3.8.0

node version: 16.10.0

OS version(s):

Steps to reproduce:

1. Go to https://npm.runkit.com/%40slack%2Fbolt
2. Click Run

Expected result:

No errors

Actual result:

Error: Cannot find module '/app/available_modules/1635904312000/@slack/bolt/dist/index.js'. Please verify that the package.json has a valid "main" entry

Attachments:

[seratch]

@brianjychan Thanks for reporting this. The npm package of v3.8.0 is not valid. We'll fix this issue as soon as possible.

[seratch]

I've published a new patch version (v3.8.1) and the one should be fine. It seems that the newer version is not yet available in RunKit (perhaps, the platform has its cache layer for npm module resolution) but I've verified if 3.8.1 works for me while 3.8.0 does not. I will continue checking if the new module version comes to RunKit and it works.

[seratch]

@brianjychan Thanks again for reporting this issue! I've confirmed that 3.8.1 is now available in RunKit and the version does not have the issue described here.

[brianjychan]

Great! I initially noticed because my deploys were failing. I'm surprised there werent other mentions. Thank you! Just curious, what was the issue?

[seratch]

@brianjychan Sorry about the disruption. The issue was some error in the publishing operation. If you're interested in details, please refer to #1195. With the new steps, we won't repeat the same going forward.

[brianjychan]

Thank you for sharing!