Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
`v2` is not working, cannot find module 'asn1.js'
See original GitHub issueIssue Description
Put up a PR to try to use v2, but it seems to be failing. This is on an ubuntu-latest runner, not in a container.
Error text:
internal/modules/cjs/loader.js:800
throw err;
^
Error: Cannot find module 'asn1.js'
Require stack:
- /home/runner/work/_actions/codecov/codecov-action/v2/dist/index.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:797:15)
at Function.Module._load (internal/modules/cjs/loader.js:690:27)
at Module.require (internal/modules/cjs/loader.js:852:19)
at require (internal/modules/cjs/helpers.js:74:18)
at o (/home/runner/work/_actions/codecov/codecov-action/v2/dist/index.js:6960:200)
at /home/runner/work/_actions/codecov/codecov-action/v2/dist/index.js:6960:391
at Object.<anonymous> (/home/runner/work/_actions/codecov/codecov-action/v2/dist/index.js:38030:27)
at Object.108.../../config (/home/runner/work/_actions/codecov/codecov-action/v2/dist/index.js:38601:4)
at o (/home/runner/work/_actions/codecov/codecov-action/v2/dist/index.js:6960:340)
at /home/runner/work/_actions/codecov/codecov-action/v2/dist/index.js:6960:391 {
code: 'MODULE_NOT_FOUND',
requireStack: [
'/home/runner/work/_actions/codecov/codecov-action/v2/dist/index.js'
]
}
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Error: Cannot find module 'asn1' when trying to run a node.js ...
I am trying to run a Node.js app on an Azure app service with Node 8.1.4. The app runs fine on my local...
Read more >npm Error: Cannot find module 'asn1' · Issue #10916 - GitHub
After updating npm version li, I wasn't abel to execute any command even npm -v here is the stack : Error: Cannot find...
Read more >Debian Bug report logs - #881292 node-asn1.js FTBFS: Error
Debian Bug report logs - #881292 node-asn1.js FTBFS: Error: Cannot find module 'asn1.js'. version graph. Package: src:node-asn1 ...
Read more >asn1 - npm
Start using asn1 in your project by running `npm i asn1`. There are 462 other projects in the npm registry using asn1.
Read more >node-asn1.js_5.0.0-2_all.deb Ubuntu 18.04 LTS Download
Package release, 2 ... Asn1.js is a pure javascript ASN.1 encoder and decoder. ... Bug fix: "node-asn1.js FTBFS: Error: Cannot find module "asn1.js", ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@briantist taking a look now, thanks
@drazisil-codecov Yes that’s correct!
For comparison, check any of the four “Units” jobs in these CI runs:
codecov@v1: https://github.com/ansible-collections/community.hashi_vault/runs/3105213359?check_suite_focus=truecodecov@v2: https://github.com/ansible-collections/community.hashi_vault/runs/3106559270?check_suite_focus=trueThe
Itests show improvement too but it’s harder to see. With just over 700 reports, the difference is something like 13s vs. 4s but there’s more variance, I suspect there’s a few seconds of overhead in the beginning either way? But yeah with a large number, the difference is very significant.Edit: the number of files is much less than I thought, looks like 8,908, I was at first naively just looking at the rough number of output lines from the action, but it seems to list the files and then process the files, so each one gets at least 2 lines in the output. Even better news I guess since big improvements can be seen with a smaller number than expected.