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.
【bug】 $(npm bin)/artillery dino failed
See original GitHub issueVersion info:
2.0.0-14
Running this command:
$(npm bin)/artillery dino failed
I expected to see this happen:
Instead, this happened:
explanation： lib/console-reporter.js accidentally has optional chaining operator, which can not be understood by node.
Files being used:
<relevant yaml/js/csv go here>
Issue Analytics
- State:
- Created a year ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Installing Artillery CLI
System requirements. Artillery is a CLI application that is installed on your computer. Artillery runs on Windows, MacOS, and Linux systems and requires ......
Read more >Common errors | npm Docs
Broken npm installation · Random errors · No compatible version found · Permissions errors · Error: ENOENT, stat 'C:\Users\<user>\AppData\Roaming\npm' on Windows 7 ...
Read more >shoreditch-ops/artillery - Gitter
The call is failing, and i'd like to see the specific error response. here's a gist ... /home/newgen/.npm-global/lib/node_modules/artillery/bin/artillery
Read more >Artillery 를 통한 NODE 환경에서 스트레스 테스트 - Hax0r
우리는 작성한 API 에 병목 현상과 얼마 만큼의 트래픽을 수용할 수 있는지에 대한 여부를 확인하고자 스트레스 테스트를 작성한다.
Read more >phase tracking error: Topics by Science.gov
Error Tracking System is a database used to store & track error notifications sent by users of EPA's web site. ETS is managed...
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
Runtime compatible code is unavoidable which could pump up the size. A waring “Please upgrade to higher node version” instead of an error would be more friendly to users. I will pull a request to optimize it.
Supporting older Node.js versions isn’t really something we want to do. We try to match current LTS or latest AWS Lambda runtime version, whichever is newer.
A smaller release bundle could be interesting if it significantly reduces package size or CLI start time for example.