Package on RunKit uses old file structure with new file content

Bug Reports
1

Package on RunKit uses old file structure with new file content.

I created my NPM package called ethavatar which is available on NPM. First, all code in this package was in one file (src/index.js), but in the last version (1.0.0-beta.5), I split the code into multiple files and src/index.js only requires them. See my package code for details.

The problem is that RunKit still uses old file structure with one file. However, it also uses new file content which requires other files. See file content on RunKit for details. This will cause an error about not resolving modules. See my RunKit document for details.

If I require version 1.0.0-beta.4, this will work because that version uses only one file for the code. However, the code would still not be useful because of unexisting module bignumber.js (details in another topic). See my RunKit document for details.

2

Thanks reaching out. I checked and RunKit is using the file structure for the package which was published on npm. You can verify this yourself by downloading the tarball: https://registry.npmjs.org/ethavatar/-/ethavatar-1.0.0-beta.5.tgz

As for your previous version not working, that’s because the web3 package you depend brings in big-number.js which is not defined as a git dependency, not an npm dependency:

“bignumber.js”: “git+https://github.com/frozeman/bignumber.js-nolookahead.git”,

RunKit currently does not support git dependencies.

Sorry for the inconvenience!

3

Yesterday I released the new version 1.0.0-beta.6, but RunKit still uses old version 1.0.0-beta.5. When will it be updated? It is already updated on the NPM website.